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. ;)
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 2 years ago.
Improve this question
A new version of Android Studio was released.
In the version 2.3 there are some news. One of those is the new ConstraintLayout.
Which are pros and cons of ConstraintLayout?
Pros:
You can develop highly complex interface, using constraint layout.
It reduces the nesting, thus overall improving the performance of your app.
It helps to be seamless across wide range of screen.
Cons:
Sometimes the result is not as expected as you want.It sometimes feel a little to track of all the all the constraint. It might get a little overwhelming for a new developer to understand the code.
Sometimes you might want to create another layout for landscape mode for adjusting the views and widgets as it may not be as you would want.
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 8 years ago.
Improve this question
In the last few days, i was trying to study the android's new Material Design. In the official doc, they suggest new element and various interactions.
But, for example, why don't they provide some simple support to raised/floating action buttons? Same to many other things, seems like they just want to suggest you the way to do it without providing real support on how to do them.
This way i end using tons of third libraries to support many of the new elements style and feels a bad idea.
Sorry for my bad english but just want to understand why can't they supply some support to the design they suggest.
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 8 years ago.
Improve this question
i want to create mobile apps for cross-mobile platforms.
Two Frameworks are interesting for me.
Kendo UI vs Application Craft.
Important for me are supporting charts. I know, that both Frameworks are supporting this but which one is better?
Thanks & Greetings
I have tried both personally (not in professional projects) and I have find both very similar.
However, it was easier to find solutions to Kendo problems than to find the Application Craft. It seems like Kendo is more community supported in terms of forums.
With both I achieved the results I was looking for, but still it took me slightly more time to do it with application craft