I am new to android tablet design.
This is the home page with its various parts numbered
I wanted to know the best possible design approach. Most sites related to android 4 describe basic use of fragments.
Here i have
1 which is fixed and would be available for all the future pages.
2 and 6 consists of sliding images.on click i want to show the images in 5
3 is the application name tab.Fixed for all pages
7 consists of tabs
4 consists of sub menu populated when a tab is clicked in 7
5 is where i want to show whatever is clicked.
My question is for such a layout, where should i use fragments and how many.which is the best possible approach.
Say since 1,3,6,2 are constant .. cant i use a separate XML and include it in the pages.
7 are the tabs. On click of a tab 4 is populated which further populates 5
Should i use fragments for these.
There are many portions in your design. The best designing style is "make it simple and avoid complexity. You always found some apps which are displaying too many content those apps are not user friendly . Just think which portion of your app is used more and more time and put it in the best position of your design .
Try to minimize the number of tabs . You can put lots of tabs on 7 and also make it scroll-able but its little bit boring to use a tab under scroll . In single activity you can not use multiple xml file with out fragment . Hare is my personal comment :" i think it would be more beautiful if you put number "7" under of over "3" and according to my consideration number "4" is less necessary , "2" and "6" is confusing "
you can see this link : Design
Thank You
Related
I am making a Education Questionnaire App.
As far as layouts are concerned, there are 10 layouts:
1 Introduction Page
2 Main Selection
3 Chapter Selection
4 Completion page
5 Question Layout 1
6 Question Layout 2
7 Question Layout 3
8 Question Layout 4
9 Explanation Layout 1
10 Explanation Layout 2
I have already made these 10 XML layouts. (The whole layout changes, so fragment not possible)
Now comes the question of connecting them with Java.
Flowchart
After the Chapter Selection Page, the user answers 14 questions(Question Layout 1 to 4)with view data changed.
Ideally, I want the back button to be used throughout the chapter so the stack will consist of 14 Activities per Chapter (1 question per screen/activity).
I need to confirm which is the best way to go about this.
Option 1
In total there are 120 chapters, so should I create 14 X 120 activities.(Sounds tiresome) Will it affect app usage speed?
Option 2
Restrict the back button to one per chapter (i.e. make one activity per chapter). Then I'll have to make 120 activities only.
In this case, in 1 activity, the 4 Question layouts will change view data 14 times (approx) with button clicks. How can I achieve this?
Search Results
I have found similar questions here but they talk about either using same layouts for each activity (Eg In Android, can I have different Activities use the same XML file?) or different view data per activity (Eg. Use single xml layout for multiple activities with different datas).
A similar question (Using multiple layouts in single activity) was asked but the answers were not implementable.
Question
My question is : Which is the better option? In case Option 2, please give me a sample. I am using Android Studio 3.0
I'm developing an Android Tablet application with Android 3.1 SDK.
I have to implement a form in an Android Tablet. Now I'm doing on one screen with TableLayout, TableRow, TextView, Spinner, buttons, etc.
At this moment I have more than 80 views and then I get a warning about it.
The form is divided into sections and I think I can divide it into tabs but I don't know if I will have the same problem (I'm very new on Android development and now I learning how tabs work).
What do you recommend me? I will have, probably, 160 view or more.
I recommend that you split this huge form into multiple screens / steps somehow, it seems much more useable and managable to me. You could use fragments to hold the steps, and use some paging mechanism to navigate between these fragments. By switching fragments and saving their state you can keep the number of Views on the screen relatively low.
Check out the ViewPager component for this to navigate between fragments by swiping. Or you may use the plain old button based navigation (next/previous step e.g.).
If you really need to display all the form elements on one screen and want to keep the number of instantiated Views, you may be able to do this by using the virtualizing ListView, though it seems quite awkward to me. ListView constructs the rows as needed during scrolling, and you need to tell its adapter that you have X type of rows where X is the number of form-parts.
Why don't you logically break this Enormous form and using something like a Next button show the form in multiple activities. This would keep the screen clean, won't bombard the user with too much of information and finally won't give the warning of excess views on screen.
in my app i am trying to implement the design of facebook homepage.
I have 7 different activities in my app. For all the 7 activities the buttons in the title(application bar) and footer part to be the same and same actions.
Now my question is, whether i have to create separate 7 layouts for all the 7 activities and i have to write the same button actions in each activity or it can be written once and can be used in all 7 activities ?
if it can be used by writing only once, how to do it pls suggest me a best way ?
You should probably create a Fragment that contains the buttons, an then reuse the Fragment in every Activity.
Check this out for more info about Fragments:
http://android-developers.blogspot.no/2011/02/android-30-fragments-api.html
you should create Header and Footer xml files separately
and then use "<include other layout>" Android Layout
to include your header and footer on each Screen.
let me clear if any doubt i have done this, very easy.
also you can check this SO thread
I have a series of 6 lists of related data. Really, they are the same set of data split out by a status flag into 6 different "Queues". In my android application I have a dashboard pattern for my main menu, which has an option for the queues. The tab strip is too small to have 6 options on it, so I would either have to have a horizontal scroll view around my tabhost (which I can't seem to get to work easily), or I need to find another way. From what I've seen, if I need that many tabs, I should be looking at a dashboard design pattern. Is it acceptable to have a nested dashboard? What is the best practice here?
In my application I want to use 4 tabs and each tab will have more than one screen. So I tried to get this and found there are two ways to do this:
Use ViewFlipper inside every tab.
Use ActivityGroup in tabs.
However, I'm not sure which will be efficient and easy way to do this since I'm a newbie in Android. So please help me.
Please post me some link where I can get sample code related to ActivityGroup.
Activities are self-contained parts of your app, views are used together when they display similar type of data/behavior.
For example if your tab 1 is taking a picture and your tab 2 is showing a map and your tab 3 is sending an email then you're better of using activities as the action are completely different, with different layouts and different behaviors.
If tab 1 is a listview with an rss feed from techcrunch, tab 2 is a rss feed from StackOverFlow and tab 3 is a rss feed from bbc news then use a viewflippers : Same behavior, same actions
THis is simple to implement
Adding Activity Group will be more preffered then adding View Flipper. By this all the code and activity contents are separated and in more manageable form plus its a stable thing to use
I have the same issue but got it totaly RESOLVED Check The Following Link
http://ericharlow.blogspot.com/2010/09/experience-multiple-android-activities.html
Changing the view within the Android Tab Widget
Its The Solution For Me . Hope It will Help You as Well