11/24/2023 0 Comments Bank account layout![]() The database is stored on the user's device. The DB consists of four tables, each with a proper primary key (composite or standard) and foreign keys when necessary. SQLite Database: All Profile, Account, Payee and Transaction information is stored in a database. The DrawerLayout is in the second Activity, which serves as the master container for most of the application's fragments. This menu hosts the different features of the application, with each option either navigation to a fragment (corresponding with the feature), or launching a dialog in some cases. The toolbar has a title that changes depending on the current fragment in use, and contains options for the user (including an options menu, back navigation, drawer menu).ĭrawerLayout: The application has a DrawerLayout, which is esentially a sliding drawer that typically comes from the left slide of the screen (either by swiping near the left edge or by clicking the hamburger button in the top left of the screen). The toolbar is consistent throughout the app, with the XML code in a styles.xml file for re-use. Most layout files are used for the fragments, while some are used for menus in the application, as well as custom layouts for dialogs.Ĭustom Toolbar: With the application using AppCompat, custom toolbars are a possibility. Well-desgined UI Layouts: Multiple layout files are used, using a well-thought design that keeps the simplicity of the app, while serving optimal functionality. Bundles are used to pass data from one fragment to another. These fragments are almost always launched from the activity that wraps them. Multiple Fragments: What the user actually sees comes from the fragments of the application. The activities themselves do not display a view, but rather host the navigation code (among other things) to travel between fragments. Intents are used to pass data from one activity to another. The activites serve as containers for the different fragments throughout the application. Multiple Activities: There are two activities: one which has the fragments for logging in and creating a profile, and the other for hosting all of the features the bank app has, including account overview, payments, transactions, etc. Additionally, there is a menu that slides from the left which includes all of the options for the app, including Dashboard, Account Overview (and subsequently Transactions), Deposits, Payments, Transfers, Profile Settings and Logout. When signed in, the user will be brought to their dashboard page, which (when first creating a profile), will prompt them to make their first account. The app starts out with a login screen, in which the user can either log in with an existing profile, or click a button and create a new profile. The Application was developed using a MVC approach, using proper programming conventions, including documentation, error/exception handling, thorough program structure and memory efficiency. No real money is involved, it is a project to showcase my knowledge and practical skill in Android development with Java. ![]() A Banking app made for Android using Android Studio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |