Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Why we call android activity visual representation of android app when it also does background tasks which have nothing to do with visual representation.
A lot of programmers consider it a bad programming style to write code for background tasks into an Activity class. When aiming towards a clean architecture one would ideally only find representational code in activities. Thus, updating the views that make up the activity. As your question implies, background tasks are better found in separate classes that make up the business logic layer of an Android app.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
As there are many techs to achieve SM in Flutter....
Which will be best as a intermediate while developing a real world app??
As for starter try to learn Provider, it's simple. No need in learning another packages. Currently, I have 2 projects based only on Provider.
It's depend upon you and your requirements. You have to maintain the state based in your scenario. All the package you mentioned, used different different approached for state management.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm recently started programming in Android Studio with Java, i don't have enough Knowledge in Building Mobile Applications.
So, my question is, if making a Class of methods for the logic of the application or make the methods in Activity Label.
Or if anyone experienced can give me a good advice.
If I understand your question correctly, it depends on where do you plan to use your methods. Are they limited to just one activity? Or will you be using those methods across several activities? If just for one activity then no need for another class to put those methods in as you will be using them in only one! On the other hand, if you plan to use the same method in several classes then putting those common methods in a single class is better
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
i want to make a Class Diagram from my Android app but I've never worked with UML in android so i have some stupid question.
Should I include all activities and classes or only class like DB_manage, preferences, etc. ?
Thanks in advance.
Activity,Fragnment, etc, it is just a system ui containers not related to your logic. You should include entities such as MVP (MVVM) interfaces, implemented by activity, fragment because it show your logic and when UI is supposed to do. Placing everything in activity is a bad practice)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I had started learning android development and have done most of the ui basics. Now I want to create my own app to know how much I have actually learned. I think all android devs started with one app so which one is the most basic app to create.
Only UI elements,
And no service, broadcast receivers and sq lite stuff. Have not got there yet
You could, for example, google out something like "My first android app"
Something like this is likely to come up:
https://www.youtube.com/watch?v=dE1b_qOx4_g
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am aware of the different methods for switching back and forth between android screens. I was wondering wich method, if any, is the best practice for doing so. Switching activites seems to be the most popular, but how processor friendly is it?
EDIT:
This question seems too objective, so I guess I will modify it by asking if anyone knows what method is most processor friendly.
Yes, apps are typically separated by multiple activities. These days, the activities contain fragments to better support multiple devices, layouts, etc. They are popular for a reason!
It's all very friendly. ;)