A mobile application capable of translating Japan's Osaka dialect into standard english.
I. Committing Section IA: Commit Guidelines:
- Updates in README.md shall always be in separate commits.
- Always pull from the Github repository first before making changes and pushing said changes to main. VIOLATION RISKS MERGE CONFLICTS.
- Before committing and pushing into main, please ensure that there are no merge conflicts in your local repository.
Section IIB: Commit Message Guidelines
- Your commit message title must be short, clean and concise. This makes it easy to see which commit did what.
- Detail all changes made in a commit message. This makes it easier to track what your commit changes in detail.
- Include the current version in your commit title. Use versioning in your commit messages such as the ff: "Bug Fixes 0.0.1-1". The format is as follows: [Commit Title] (AppVersion)-(Nth commit number in that version.) See this for reference. This makes it easy to see which commit belongs to what version. Updates in the README.md files doesn't need this.
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter development, view the online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.