Have you ever used one?
I'd love to speak with you so I can understand the needs of someone using a boilerplate! Promise I won't sell you anything
Have you ever used one?
I'd love to speak with you so I can understand the needs of someone using a boilerplate! Promise I won't sell you anything
4 comments
I agree about the marketing but as I'm still not sure if it's regular devs (most like coding stuff themselves). Also, I'd need to find a distribution channel...
Of course, I don't expect you to share your knowledge on that hahah
But basically copying functionality that takes a while to build.
1. Design system [1] that's integrated with Compose. Meaning blocks are built as part of other blocks.
2. Networking and caching - these can take half a day to assemble and debug.
3. Test integration. Easily days or weeks to do on Android, because dumb stuff like some misaligned libraries.
4. Dependency injection, also harder to set up the larger code gets.
[1] https://bradfrost.com/blog/post/atomic-web-design/
I just copy the folders over after creating a new projects.
I'm sure there are better ways
Well, it's one thing you can create with https://hofstadter.io/docs
I bought one on Webflow, but have since moved off their platform to Hugo, which has themes (same idea) and where some are paid too
I don't call out "living boilerplate" as a section in the documentation, but I think setting up a generator module with just static files should suffice. Certainly you can get more fancy if you want your users to provide some inputs.
Happy to help or show you this in Slack or a video call.
I'm planning a *create" subcommand to make this even easier for those who would use your boilerplate. It will have an interactive first time experience like react create-app