ThePuiu Active Member Licensed User Longtime User Apr 1, 2014 #1 I need to write an application that is starting with a login screen. From login screen you can go to the main screen after authentication. From here you can navigate to other 3 screens containing various information. How do I properly design that application? One Activity for each screen, each with multiple layouts for different resolutions? Is that ok? Thank you!
I need to write an application that is starting with a login screen. From login screen you can go to the main screen after authentication. From here you can navigate to other 3 screens containing various information. How do I properly design that application? One Activity for each screen, each with multiple layouts for different resolutions? Is that ok? Thank you!
NJDude Expert Licensed User Longtime User Apr 1, 2014 #2 Android's preferred method is 1 activity per screen; regarding layouts for different resolutions, use the designer scripts. Upvote 0
Android's preferred method is 1 activity per screen; regarding layouts for different resolutions, use the designer scripts.
ThePuiu Active Member Licensed User Longtime User Apr 1, 2014 #3 Which is the top 3 most usual screens resolutions and densities? Is ok if I make one layout for each one of this resolutions? How many layouts must exists to can affirm: This app can cover almost all devices! Can I choose the right layout in concordance with Activity.WIDTH and Activity.HEIGHT? How about density? Upvote 0
Which is the top 3 most usual screens resolutions and densities? Is ok if I make one layout for each one of this resolutions? How many layouts must exists to can affirm: This app can cover almost all devices! Can I choose the right layout in concordance with Activity.WIDTH and Activity.HEIGHT? How about density?
NJDude Expert Licensed User Longtime User Apr 1, 2014 #4 No need to have different layouts for each resolution, just use the designer scripts, that will cover all the devices. Upvote 0
No need to have different layouts for each resolution, just use the designer scripts, that will cover all the devices.
ThePuiu Active Member Licensed User Longtime User Apr 1, 2014 #5 Ty for the reply! Now I have another question...a simple EditText in Android 3 appears with a black border around it, and in Android 4.3 is completely transparent... How can avoid this different behavior? Is a solution to put the EditText inside of a image with a border? but then I must check which kind of OS is installed and activate the image only for version > 4 ?!? What is the best practice? Upvote 0
Ty for the reply! Now I have another question...a simple EditText in Android 3 appears with a black border around it, and in Android 4.3 is completely transparent... How can avoid this different behavior? Is a solution to put the EditText inside of a image with a border? but then I must check which kind of OS is installed and activate the image only for version > 4 ?!? What is the best practice?
NJDude Expert Licensed User Longtime User Apr 1, 2014 #6 I think you need to read some documentation my friend But, to answer your question, that happens because the HOLO theme which was introduced on newer versions of Android, if you want to keep the same theme on all the devices, then target SDK < 11. You can find all that information by searching the forums. Upvote 0
I think you need to read some documentation my friend But, to answer your question, that happens because the HOLO theme which was introduced on newer versions of Android, if you want to keep the same theme on all the devices, then target SDK < 11. You can find all that information by searching the forums.
ThePuiu Active Member Licensed User Longtime User Apr 9, 2014 #7 The attached chart is the information flow of my application. Now works correctly but I want to know if it is the correct approach. I would like to navigation BACK to not lose data entered in the previous step. For this I have to use the StateManager? Attachments Untitled.jpg 66.8 KB · Views: 386 Upvote 0
The attached chart is the information flow of my application. Now works correctly but I want to know if it is the correct approach. I would like to navigation BACK to not lose data entered in the previous step. For this I have to use the StateManager?