Very Simple Design
This application will be used to track the daily weight of the user. This application must include the following:
A database with at least three tables: one to store the daily weight, one to store user logins and passwords, and one to store the goal weight. Note that goal weight will be constant but setting a one-time weight that is stored in a database will be the simplest way for you to accomplish this task.
A screen for logging into the app; note that this should also be used to create a login if the user has never logged in before
A screen, with a grid, that displays all of the daily weights and the days they were entered
A mechanism by which the user can add a daily weight
A mechanism by which the user can add a goal weight
A mechanism by which the application will notify the user when they reach their goal weight
App Code Design
Develop code that allows a user to log in. As you develop your code, use the Android Emulator feature of Android Studio to test your code. Your app should work for users that both do and do not have accounts. This means you should focus on the following functionality:
The app should check the username and password against the database when the user attempts to log in.
If the user has never logged into the application before, the user should be able to create a new login and password. The application needs to save these to a table in the database.
Develop code to create a database shell and display that database’s information on a user’s screen using a grid. The SQLLite database you create will depend on the option you selected in Project One and will store either inventory items, event details, or daily weight. Any information needed for your application to function correctly should be held in the database, but remember you are only creating the shell for the database so its contents can later be populated by a user. Note that you will need tables in the database to store user information when it is not being displayed in the grid. This database will be persistent so no user information is lost when the app is closed. Be sure to test your code often with the Android Emulator. Your completed database should allow a user to accomplish the following:
Create: The user should be able to add items to a database.
Delete: The user should be able to remove items from a database.
Update: The user should be able to change the value associated with individual database items (e.g. the number of a specific item in an inventory or the date of an event).
Read: The user should be able to view all of the database items displayed as a grid.
Develop code that prompts users for permission to send SMS messaging notifications and makes the app function based on the individual user's response. Keep in mind that the user of your application might deny access to the permissions needed for sending text messages via SMS. If they do, your application should still continue to function, just without this feature. Test both possible options for user response by using the Android Emulator. When you do, you will be looking for the following outcomes:
If the user grants permissions, the application should send alerts to the user as SMS messages. The alerts correspond to the specific notification trigger of the application you chose (low inventory, an upcoming event, or reaching a goal weight).
If the user denies permission, then the rest of the application should still continue to function without the SMS messaging notification feature.
3 freelanceria on tarjonnut keskimäärin 133$ tähän työhön
Hi,I developer and Analist professional with experiency in JAVA I konw Android Manager Database Mysql Please me contact and I can help you best regards