Hi everyone as the title say I am wondering whats the best practice to design an android app should I make multiple activitites for each interface in my app or one activity that has multiple fragments(note:I am using a navigation buttombar)
Depending upon your need you can choose between activities and fragements. Activity is more like a complete separate page and fragment is a small view that can be called in an activity, multiple fragments can be used to display activities UI .
Fragments can be used to make dynamic views check this link https://developer.android.com/training/basics/fragments/index.html. Hope this helps :)
Related
For example, I have activityMain which contains the main logic of the Application, but it should be opened from several buttons that stored in other activities, and some activities contains multiple buttons too. And they should call activityMain. So i need to pass different data from db depending on which button called activityMain
Help please, there weren't similar topics at all.
If i Understand your question correctly, you can achieve this functionality with android jetpack navigation component. I add the link of documentation below
Get started with the Navigation component
I am beginner to android..I am started new android project..for supporting
different screen size..in fragment documentation they given to use fragment..but
why cant i use activity in android..if i use activity or fragment..which i should i use in this both..please dont give link of activity or fragment..please anyone answer me..i dont know which to use?...i want about all documentation they given about activity and fragment but i dint understand which to use..below is the link i read about fragment..if i use activity i should do more codings?
https://developer.android.com/guide/components/fragments.html
In fact you can't use a Fragment alone, Fragments are inside the Activity.
One point of using the Fragments for supporting different screen sizes is the ability to implement some views like a "Master/Detail" view.
A Fragment, as its name says, is a part of a bigger controller "the Activity", its reference can be removed and it's cleaner than having a big massive Activity to handle all the states of a view.
So the use case is completely depends on your project and its User Interface. I'd be glad to help you if you give me more information about your project and its design.
I think you will need at least one activity. And then for better handling different device rotations and screen sizes you can use one or more fragments inside this activity.
I try to explain this with an example:
You want to create a nice music player app which should look nice in portrait and landscape mode.
You split your app up into three fragments:
Here you can see how the app looks in portrait mode. The activity shows two fragments: The first fragment only consists of a listview. There the song titles are listed. On the bottom you can see the second fragment, which displays the song title of the current playing song and got a button for pausing the music.
When your user uses the music player app on a tablet in landscape mode you have more space for displaying stuff. Then the activity shows the list fragment (which also gets displayed in portrait mode) and it shows a third fragment which shows detailed information about the current playing song (e.g. the album image) and a progress bar.
By using fragments you only need to write the code for the list once.
Sweet and Simple thing, What i recommend is always use Fragments,
But for Fragment you will require Activity.
Take it in this way , Activity is a Canvas on which you can put any number of Fragments.
Whatever your UI is always use Fragment present on a activity if you want to show one screen even then also, So that you will always have Flexibilty to use all those cool things which fragments provides,maybe in future or in current.
If you use activity it has limits,FOR EXAMPLE, LIKE in INSTAGRAM AT BOTTOM, It has FIVE OPTIONS, Suppose THOSE OPTIONS ARE ON A ACTIVITY AND BY CLICKING ON THEM YOU CAN SWITCH TO DIFFERENT FRAGMENTS.
For more info:
Here is the most accepted answer for this topic.
I'm new with android apps development (but have some Java experience) and I am struggling a little bit with how I should design my app. For example:
When I execute the App I have a start page with the logo and two buttons: Register and LogIn. This should be the first activity.
1.) If I press the register button I see a page (another activity) with the input fields, a register button but also a Facebook and a Google+ Button.
2.) If I press the login button I see a page (another activity) with the input fields, a login button but also a Facebook and Google+ button.
Instead of implementing the facebook and google+ button twice, I thought about putting the google+ button and its functions into a seperate fragment and the same for the facebook button so I can reuse them.
Is this a "good" interpreatation of activities and fragments and if not when should I use fragments and activities? I thought about fragments like reuseable containers which can be implemented in different activities.
Thanks for any advice!
Activities, fragments and views have very similiar purpose, but on different levels. You can freely mix them as you wish as long as it's working for you. Personally I don't like fragments, so I'm only using activities and views in my apps. Here are the main differences:
Activities are the entry points. You can start your app using Intent to one of it's activities. You can't do that with other elements. You should use an activity when you plan an entry point. For example an email composing module which can be accessed by other apps.
Views are very light and simple. Use them to prepare reusable components, layouts and widgets. Views can be accessed by other apps only in a library form.
Fragments are somewhere in between. They consist of visual parts, data and application logic. Fragments can be used with backstack manager like activities, can't be launched using intents, can make use of layouts and widgets like views. Use fragments to create larger screens with backstack.
And similarities:
All three mentioned elements can be displayed multiple at the same time. Activities using ActivityGroup, fragments using layouts and FragmentManager, views using layouts.
All three have their lifecycles. Fragments have the most complex lifecycle, views - the most simple.
All three can be used to compose applications. You can place layouts and widgets on screen using activities, fragments and views in a very similiar way.
Basically activity consists of a window and a layout (and some data & logic). Fragment consists of a layout (and some data & logic). View is a layout or a widget (and some data & logic).
Answering your question - This means that your approach is fine. At least for me. If you plan to reuse these buttons only as a UI components, you can rewrite them as views.
I am building an app with a drawer layout similar to the Android Facebook app. I am wondering what the best method for architecture is. Should I have a main activity which is responsible for the action bar, and then have it use fragments to display the content of each menu item, or should I be using one activity to manage the action bar, and then have each menu item kick off entirely separate activities?
I could also imagine building multiple activities, which each have to manage the action bar. This option seems the worst.
You have two architecture options here
MainActivity with Fragments
ParentActivity that handles drawer and lots of Activities that extends this Activity.
I have tried both in different projects and found some things worth sharing.
For me The MainActivity that handles drawer and then using Fragments to fill the display is the best.
You will need to handle callbacks from specific Fragments in your MainActivity and redirect them to the specific Fragment they came from. This is mainly if you use Interfaces in objects lower in the Arcitecture chain since you sometimes need to pass down Activity to certain objects. This generates more code that are not as generic as one might want in top level architecture node.
If you are using a ParentActivity and extending it for each ChildActivity, you can write all specific code in the child, meaning that the toplevel ParentActivity will almost only have generic code.
If you are using the ParentActivity with ChildActivities and you are switching between Activities, you fill get the graphic when an Activity closes and the next opens every time a user switches between navigation objects. If you use Fragments this wont happen as the Fragment will be switched in the background. The user will also experience that the navigation drawer will be closed and recreated each time he clicks on an item there.
Its also unnessecary to recreate the navigation drawer with each click on an item. This is a minus for the ParentActivity approach.
With the ParentActivity approach you will also have to keep track of how the backbutton should function, this will be autoaticly handled for you with Fragments. Also when starting new Activities you have to choose if a new Activity should be created or if the old should be killed etc.
Just my 5c, hopes it helps :)
The best way is to use one Activity with one Fragment per section/view.
Take a look at the design documentation.
Also see the Tutorial and Sample Application. It's fairly straight-forward.
You will have one activity which manages ActionBar, Drawer (ListView!) and Fragment.
Every time it clicks an item in the ListView it updates the fragment with the new view.
If you use different Activities then you should use intents with a very bad effect, use a different activity only if needed (if it's totally unrelated to the current activity maybe?)
Official documentation: http://developer.android.com/training/implementing-navigation/nav-drawer.html
If you got any problem in creating this, online you can found more tutorials but the official is very great.
You should have the activity holding the actionbar & drawer
When using a drawer you should not start new activities from within the drawer but fragment instead
Good post & video about it: https://plus.google.com/u/0/+RomanNurik/posts/3nMVVQzUTjG
another good read: http://www.androiduipatterns.com/2013/05/the-new-navigation-drawer-pattern.html
And finally this is a must see also (check the slides or the video): https://plus.google.com/u/0/+NickButcher/posts/1jeyV2n1ZpM
I have a tabbed interface for my program - there are two tabs: take photo and view photos.
As the name suggests, the user can take a photo in "take photo" and the user can view photos taken in "view photos". Right now the way its set up I use one single MainActivity and I have TakePhotoFragment and ViewPhotoFragment -- question is: does this contradict the principles in which Fragments are supposed to be used in? I don't really anticipate having both fragments displayed in a single screen (e.g. on a tablet), but I don't see how I can use one activity for each because of the limitations of the tabbed interface (when I created the activity in eclipse, I was prompted to select what kind of layout, I chose tabbed layout, and automatically code for fragments within an activity corresponding to several tabs was generated)
Can anyone help? Should "take photo" and "view photos" be fragments or activities?
It should definitely be fragments.
This does in no way contradict anything, plus I do not understand your concern about showing both fragments in a single screen. If you do not want that to happen, you just program accordingly. That is certainly not something that just happens because of the choices that you have mentioned so far.
Fragments is the best method you can use for the purpose you mentioned above. You can check the below links to know about the usage of fragments.
Creating a fragment
Fragments
android fragments
android fragments tutorial