CompetencyIn this project, you will demonstrate your mastery of the following competency:Apply user-centered design principles and industry standards in the development of a mobile applicationScenarioCongratulations! Your App Development Proposal has received approval after being shared with both your client and the mobile application development team at Mobile2App. It is now time to construct a UI based on your original proposal. You must supply the client with a complete UI design that is easy to understand and demonstrates a creative theme and layout for the finished application.DirectionsOpen the Android Studio Layout Editor to begin creating the UI for your app. Be sure to use the Install Android Studio resource and the Build a Simple User Interface resource, both linked in the Supporting Materials section, to get started with this software. Throughout this project, continue to reference the App Development Proposal you completed in Project One while paying particular attention to the section on UI Design. Also be sure to let the Android Design and Quality Guidelines document, which is linked in the Supporting Materials section, guide your decisions.Your completed UI should include all of the screens needed for your app to operate but the UI will not yet be functional. You will only be creating the UI components for this project as the supporting code will be completed in Project Three.Create UI with appropriate design elements to support a user logging in (1 screen). Your UI must include a login screen, that contains the following:Fields for the user to provide a username and passwordNote that the password element should be configured in a way that obscures any text that is typed into the field. This means the text will need to be visually converted into dots.A button for the user to submit their username and passwordA button for the user to create a new login if it is their first time using the applicationNote that to simplify the account creation process, you can use the same login screen for this purpose. Create a button that will add the username and password into the database if it does not already exist.Any other fields or elements that are necessary to make your application visually appealing, intuitive, and usableCreate UI with appropriate design elements to display database information as a grid (1 screen). Your UI must include a data display screen, that contains the following:A grid for displaying dataLogical labels and headers for the data that will be displayedA button for adding data to the gridA button on each row for deleting that row of data from the gridA mechanism that allows a user to change the value associated with each grid item (e.g. the number of a specific item in an inventory or the date of an event)Any fields needed to add data to your grid, though this can be on a new screen if you feel the layout is better for your appCreate UI with appropriate design elements to prompt a user for permission to communicate with the text messaging app and display information based on permission (1 screen). Your UI will need to include a button, or alternate mechanism, that would cause the app to ask a user for permissions so it can communicate with SMS messaging. A user that grants permission will then receive automated system notifications based on which option you chose in Project One. These notifications would be low inventory, an upcoming event, or reaching a goal weight. If the user denies access to the permissions needed for the app to interact with SMS, then your app should still continue to function overall but should not provide any notifications.Develop visual hierarchy and consistency between UI elements on different screens. The layout for each screen should follow an intuitive visual flow, have a consistent theme, and be creative but still easy to understand. Ask yourself the following to help determine if your visual hierarchy is successful:Does my focus order match with the steps a user would follow when completing a task?Does my grouping organize content in a way that makes sense for the user?Do my transitions have consistency between screens and tasks?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.Employ industry standard best practices such as in-line comments and appropriate naming conventions to enhance readability of code. This should be evident throughout all of the code you create for this project and will be assessed comprehensively. Some things to ask yourself as you code are:Have I kept my classes concise?Is my style consistent throughout the code?Would my naming conventions make sense to anyone else who looked at my code?Do my in-line comments contain enough useful information?What to SubmitTo complete this project, you must submit the following:APP UI DESIGNYour final design should be submitted as a ZIP file including the full contents of your Android Studio project. Remember to title the file with your name and the app option you previously selected.Supporting MaterialsThe following resource(s) may help support your work on the project:Install Android StudioUse this guide to download and install Android Studio depending on the operating system you will be using.Build a Simple User InterfaceFollow these instructions to access the Android Studio Layout Editor from Android Studio to begin building the user interface.Android Developers - Design for AndroidYour app will need to meet specific requirements so it will look and behave in a way that is consistent with the Android platform. This website details the material design guidelines for visual and navigation patterns along with the quality guidelines for compatibility, performance, security, and more.Material Design AccessibilityThese visual hierarchy guidelines set forth by Material Design will serve as a useful reference when creating focus order, grouping, and transition

How have the Internet, intranets, and extranets affected the types and uses of data resources available to business professionals? What other database trends are also affecting data resource management in business? What types of databases and web-based networks have you used in your business experience (current or past)?