Best practices for sharing our custom view
We should always aim for the highest quality possible, even though we're building a custom view or component only for ourselves or for a small application. However, there are some additional checks and best practices that we've to take into account if we want to share our custom view so others can use it. If that is our goal, and we'd like to get as many developers as possible using it in their applications or contributing to it, it'll be quite challenging to involve them if we ignore these basic recommendations.
Considerations and recommendations
Something we should consider is that once we share our custom view, it might be used for many Android applications. If our custom view has errors and crashes, it'll crash the application using it. The application's users will not consider the custom view at fault but rather the application itself. The application developer, or developers, might try to open an issue or even submit a pull request to fix it...