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'm trying to prepare a set of guidelines and project template for my future Android projects. Im already implementing the basic MVC architecture modularity. Im trying to have add more advanced level of design to my Android projects to make my development easier and maintainable.
For example can someone suggest me a way to make Intent calls to Activity without explicitly mentioning the class while creating the Intent. Im trying to loose couple the intent calls and hopefully use AndroidManifest to assign action to an activity which then can be called globally within the application.
Any other type of suggestions are welcome.
Also please suggest any kind of coding conventions that you might be using yourself.
if you want to call an Activity without explicity set the Activity class in the Intent you could register a broadcast receiver in your activity for your custom action..
Have a look at registerReceiver function.
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.
This post was edited and submitted for review 1 year ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
I'm here looking for the best practices in Jetpack Compose, what is more best practice, work using new Activity (by using intent)
startActivity(Intent(this, AnotherActivity::class.java))
or using Jetpack Compose Navigation?
and please show me the example why it will be best practice like, Time Compile, or Memory to run the app.
Thank you for your answer...
Jetpack Compose is built for single activity architecture what that means is you only have one activity and use compose navigation for navigating in your apps it is much easier also but if you need to use multiple activities you can but the data passing falls on your hands you need to take care of it.
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 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 6 years ago.
Improve this question
I'm a beginner in android. I learn the basic concepts one at a time. But now i'm trying to make a slightly large project. How should i approach this? Should I make all the activities first or should i make activities along with code? Or should i just continue on with the anything i like?
The first thing you would need to think of is what exactly your app does.Once you have that in mind the next thing your're going to want to do is think of an interface for the app which usually leads to deciding what information needs to be shown when and on which screen.Once you know what needs to be where you can start the actual coding,i suggest 1 activity at a time.
If you want a large project i suggest a to-do app.
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.
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 9 years ago.
Improve this question
I am new to android and I would like to write a "Social" android application that would require voice calling between two phones. How should I approach this? Or would it be easier if I "outsource" the voice calling part to another program like Skype?
Thanks!
The quick easy solution is to use the ACTION_CALL intent and use whatever default calling application the user has. If you want to do the whole thing in your app Twilio has a pretty good SDK, but I don't know that I'd recommend getting into that on your first android app..