Have you ever dealt with the frustration of trying to find an Android library, but anything and everything you find is either buggy, deprecated or just doesn’t fit your requirements?
It may be some kind of view, or some way to animate views, or an easier way to store data, could be anything. In that moment, you’re stuck, and so you think to yourself - why don’t I just build this myself.
Since I’ve been through this turmoil before and have somehow successfully created a custom view from scratch, I thought why not save the world some trouble!
Writing code for custom views can be tricky business. But making the decision to write custom views or go with default ones is a bigger dilemma.
Occasionally, when required to build a complex layout, we get to a point where we find ourselves at a clear crossroads. We are faced with two options, and choosing one is never easy.
One option is lucrative - easier to code, and quite possibly faster. This route requires using a bunch of default android views.
The other route looks more complex - requiring more coding prowess, taking up more time and seeming more difficult…