how to create a new component in android studio 2.2.3

Since writing reusable components is like writing complex new features. Finally, I have not tested this theory but IMHO if you’re bored and you feel like making an old legacy project interesting.If your teams plans to build extremely custom view like karaoke, piano keyboard, fancy animated overlays, etc.Again, pitch the team to sustain consistent user experience.

Otherwise, reusing them will be challenging. Those views should have fairly similar UX/UI to serve as a reusable components. If you see one (or more) view is used (will be used) in many places (reused).If you’re in a flexible environment where design decisions are done based upon many perspectives (not just your own) so you can pitch for good UX/UI.The following list should help you making a decision.ĭefinitely a hard nut to crack. It is sometimes also hard to let go of technical nicety such as custom views but please be mature to do so. I understand it’s hard to draw a line between MVP/short-term and a long-term project sometimes. IMHO you should be a part of a bigger, long-lasting project to consider doing so. You can jump to the second part for the list of recommendations.įirst, ask yourself a question: Do we need reusable components? The first part says why and when adapt such technique. There won’t be implementation details (code) for many reasons, one of those is my trial to focus on the concept rather than technicalities.Īnyway, I hope that after reading this article you will be able to apply those principles to any interface architecture pattern such as MVP, MVC, MVVM or MVI.

I will provide the basic reasoning behind architecting custom reusable views. And those who had problems with finding good guidelines on the topic. How to start writing reusable components for Android apps?įor anyone, like myself, interested in building custom, reusable view components for an Android app.

How to create a new component in android studio 2.2.3