| Then I'd say focus on the speed, and drop any references to these "problems" that don't really exist. So, I still don't know how much pain your customer is in. You've said "yeah, not a problem for React Native", but there are other environments that people develop in too. What about Flutter? Etc etc. So I'd say be clear about what dev environments you help with. You say "fast" and then describe the hardware. That's not the way you want to pose that. I had to look at what my machine is...2GHZ & 16gb Ram. What you want to describe is how much pain your user is currently in, and how much you can help them. You do say "Save 20 seconds", and that's good, but is it 20 seconds on a 40 second build? Or on a 5 minute build. How painful is that 20 seconds. If it's saving you 50% of the time on a build, that's good. If it's 5%, probably not so good. And still, it's 20 seconds! If it was 20 seconds on an auto-refresh type situation, yeah, that's annoying. If it's 20 seconds like a test runner, might not be as big of an issue. Can you frame this in such a way that even somebody who doesn't build using Java/Kotlin can understand the pain you're solving? Can you make somebody who doesn't have the problem want the solution anyway? As I alluded to in my first comment, saving 20 seconds might be helpful, but it needs to be helpful enough to overcome the inertia and familiarity of continuing to do what I already do. Hope that helps. |