Describing problems solved on development framework
Hey, I'm currently building a landing page for our product Liteflow. It's a development framework and serverless backend built to help developer-entrepreneurs build and ship faster, and manage less.
Below are some of the problems solved. Do you think these are too technical, not technical enough, not personal enough? Anything else?
- Eliminate repetitive code
- Communication between services is automatically managed, eliminating all boilerplate code for API creation, server routing, authentication, etc..
- Collaborate easier
- Applications are split into separate components with specific objectives, making collaboration and maintenance headache-free.
- Lower barrier to entry
- With only a few lines of code, developers of all levels can manage the interaction between reusable components, then host their applications right away.
Thanks for your feedback. Any and all is welcome. :)
Trending on Indie Hackers
Coming to this as an experienced software engineer myself, I find the first point about repetitive code most compelling.
Without digging any further, I'm not convinced on the Collaboration point. Github is a collaboration tool. This looks more like a tool for organizing serverless functions and API endpoints.
Lower barrier to entry strikes me as a managerial concern. You may want to consider different landing pages for different audiences.
On the landing page, that screenshot of code is really interesting to me, and tells me a lot more than the copy does (again, experienced web dev here). The copy feels pretty generic. Every framework promises this. Contrast with the Django web framework's tagline, "Django: The web framework for perfectionists with deadlines."
Who's your audience? Get very specific. (Have you developed customer personas? Look into empathy maps if you haven't.)