Ah ok, apologies. What will your app do?
In terms of the work flow/architecture, then obviously the first thing presented to the user should be the login screen. This should also provide the ability to create a new account, which would take the user to a separate screen for entering details.
Once past this login stage you are into the main app, and the work flow or behaviour will really depend on what the app is doing. For my last app I adopted a tab based UI, as the functionality could be partitioned into distinct areas. It made sense for these to be shown on different tabs.
I also made use of the action bar to show various icons, which could be made dynamically (in)visible, depending on what the user had selected on the screen.
You would do well to first sketch out your required screens, to design the layout. This will help to clarify the work flow in your mind, and also to flush out any details you may have overlooked.
It's a very creative and enjoyable process to see your app take shape and do something useful.
This entry passed through the Full-Text RSS service - if this is your content and you're reading it on someone else's site, please read the FAQ at http://ift.tt/jcXqJW.
just starting android, need help with SQLight ?
Aucun commentaire:
Enregistrer un commentaire