I am new to android MVVM architecture. Can I get any sample project from where I can follow folder structure for the implementation. I want to call REST Apis from the app. But I didn't find any good sample. Please let me know any good projects ti refer (Apart from google samples)
Like others mentioned, Google would be the first place to search this kind of stuff. As you mentioned, there are MVVM samples provided by Google on GitHub. However, they are a bit complicated to understand due to the project being really large. I believe this that this sample project is much easier to understand and does a good job explaining MVVM: https://proandroiddev.com/mvvm-architecture-viewmodel-and-livedata-part-1-604f50cda1.
Hopefully this helps!
Related
I have basic understanding of java and how classes works.
please guide me in the right path.
kindly give brief summary of steps that i have to follow in this journey.
Look at this website. I find it quite useful- https://roadmap.sh/android
Here's the Android Developer Documentation. Considering that Kotlin is the preferred language to use for Android development, I would suggest expanding your knowledge of object-oriented programming in Kotlin rather than Java.
The documentation provides links to guides/tutorials that will walk you through the basics of an Android application while also establishing proper coding practices in Kotlin. I personally find the docs very useful in this regard, as I'm currently refactoring a legacy app written in Java.
I recommend using the google codelabs to learn topics, these codelabs are updated by the Android dev team use best practices. If you are just starting out I would recommend learning Kotlin over java, Kotlin is the recommend langue by the Android Dev team, Kotlin takes advantage of coroutines.
Here is the Android dev guide for beginners, I would work through these modules. I still refer to them from time to time.
https://developer.android.com/courses/android-basics-kotlin/course
I've been through the SODA Android SDK's GitHub page, and README.
Is there more developer documentation or is this it? If this is it, is it common to find light-touch documentation like this? and is this is recommended to read the actual source code to understand what's possible?
The soda-android library is actually pretty old at this point, and I'd recommend instead just building a simple client using the Retrofit library on our RESTful API. I've heard great feedback about using that library with our API.
In the last period i am having the chance to develop some apps for personal reason, and taking a look to what today the companies are organizing their work in the Android Ecosystem i encountered many and many times this kind of project configuration:
MVP (Model-View-Presenter) as Design Pattern for app architecture;
RxJava for Reactive programming event-based;
Dagger2 for dependency injection;
ButterKnife for fields binding with annotations, used in combo with Dagger2 in order to make your life simplier;
Espresso and Mockito for testing (really nice to use in this kind of environment with this kind of settings)
So, is this becoming a new standard, in your opinion? If so, do you think that is a good idea apply this (relatively) new guidelines and you usually use this kind of project tools/pattern/libraries into your apps or you think there is something better? If you don't like, it, why? What do you think could be a better approach?
(Obviously each project is different, and for each project is always better engineerize the best solution/architecture possible for the kind of users/team/dev involved. I am trying to understand/discuss this kind of model that seems to become widely used in his concept in many, many companies)
Thank you for your time, i hope to create an interesting discussion on the argument in order to all improve our skillset/projects.
Enjoy your day!
We can not say above methods as standard because Android-Sdk does not have any official support from its Libraries and API's. But As far as development environment is considered now a days Developers are using these methods for writing better code base for their apps, better understanding for future development.
As per my knowledge using these libraries is useful only if they have good support from developers as these are open source libraries. For example I am using AndroidMVC right now for MVP pattern. As per my knowledge this is very good library as I am using it since last year but As there is only one developer working on that library, it's very hard to get support for bug fixes(forget about enhancements).
So while selecting any open source library you should always look all the parameters like support, enhancements, bugs etc.
Libraries like Glide, ButterKnife, OkHttp, Couchbase lite, retrofit, Volley etc are some evergreen libraries of Android.
But again OkHttp, Retrofit and Volley are used for similar purpose i.e. for networking. Now developer have to choose according to pros and cons of each library.
As far as question - should we use libraries or not? is considered. I think YES. We should use these kind of libraries which are stable because it saves lot of time and it's not of use rewriting the code if we already have it in form of library.
According to this link www.androidbootstrap.com/ I am wondering what does it really do, what is for? Am I supposed to use it?
I've read all text on this main page but I am still confused and I do not know should I use it.
The main problem is I don't see the point. Could someone tell me what is it for?
I am open for new technologies but here is the example where I don't understand, but they say that using their package will shorten my work on application.
Regards and I am looking for any information.
I am wondering what does it really do
It generates a skeleton Android project containing specific libraries. It is reminiscent of the new-project wizard in Eclipse, just supporting more third-party libraries, particularly ones that may be a bit of a challenge to get working together.
I had a look at this project to provide a quick set up for actionbarsherlock and dagger DI.
I think it’s a good idea as it seeks to provide an android template, with an out the box solution including sherlock and dagger. But I couldn’t get it working on eclipse, and the forum had a lot of people saying the same (I think its designed for Intelij IDEA)
I also looked at androidkickstartr which is more mature, but again had import issues, so just made my own template and imported sherlock and dagger
I am developing android game using opensource cocos2d-android-1 library available here . I also developed demo application using this tutorial.
Now I want to do further development but I am not getting any documentation for this library and how to use library. If anybody knows any blog, forum, documentation for this library project please suggest me.
I recommend you use cocos2d-x instead. It is also a port of cocos2d-iphone but with more platforms, a better documentation and a wider community than cocos2d-android (but still not as good as cocos2d-iphone).
It's probably a bit more painful to start because you need to understand how to run native code on android but you probably won't regret it when you decide to port your game on another platform.
many example is available on the github for cocos2d-android and documentation is not in large scale but you can handle most of the things from the test sample which is available in the cocos2d-andriod . if you getting any problem ..post here to get the answer or help..