S
S
Saymon_K2015-07-16 08:50:45
Android
Saymon_K, 2015-07-16 08:50:45

What is your take on creating your own widgets in Android?

I am a beginner android developer. And during the execution of one simple project, when I started thinking about the design of the application, the idea arose not to use, for example, SearchView to create a search in the ActionBar, but to make my own widget with my own implementation, in no way connected with the standard Android (i.e. I myself create EditText and everything else). It seemed convenient to me, because you can turn back whatever you want, change the design as you like, etc.
But the following question appeared: in serious, large projects, do normal programmers do the same or somehow use a standard widget, just change its components a little, inherit and override some methods?
Maybe it's better not to create a bicycle and change the standard widgets? Probably, it will be better, more reliable, more stable? Or still create your own?
I hope I was able to explain what worries me. :)

Answer the question

In order to leave comments, you need to log in

2 answer(s)
X
xmoonlight, 2015-07-16
@xmoonlight

We take the original skeleton of a standard widget/component, cut out the excess (if necessary) and build it up as we need.
This approach is used in all programming languages.

H
hummerd, 2015-07-23
@hummerd

A good programmer is lazy. He doesn't write too much. If the standard control does not meet the requirements - design (and this cannot be corrected with styles) or functionality - rewrite. If you want to bet on the future - suddenly you need it - no! Not needed (YAGNI). But you will waste time and the manager will think that you are a brake, and colleagues will think that you are complicating everything. And if you just really wanted to try to rewrite, gain experience, try your hand - this is at home with your own pet project in your free time.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question