[surfertas]

First off, thank you for taking the time reply.

I would be ecstatic with 1000 users, and would definitely give me motivation to continue to build. Out of curiosity what was the state of the 1000 user 1st month vs. 200 user 1st month? Were they both pretty much complete apps? Or still in a MVPish state?

I was torn between spending more time developing before releasing or get some sort of validation to avoid the “building a solution for no ones problem”, and really was getting drained spending hours on developing. Maybe a bit of burnout being a solo dev working on this. I wanted to be reinvigorated by some level of validation.

Generally feels like the bar for getting any validation/feedback is higher, as the general consumer wants a shiny, not buggy, fully functioning app before even dipping their toe in.

Agreed its not 10x better for most people, but do think there is a convenience factor and some price that someone might be willing to pay for that maybe not 6%, but the 6% covers stripe charges (processing & payouts to connected accounts)

With regards to the pushing fee to customers, my logic was that a possible user would be pushed off by the 6% charge, and not even try out the application (albeit everything else about the app is pushing them away anyway!)

Thanks again.

[muzani]

The app with 1000 users was horribly buggy. Statistically, it crashed 3 times per active user per day (memory leak with photo scrolling). But the thing is that it was crashing 3 times/day and not 1 time/day, meaning that users kept using it. This was 2015, but even today, I'm working on a glitchy unpolished app, and customers just keep using it.

The app with 200 users is http://random-character-generator.com

So generally, I disagree that customers want something fully functional. But fintech is a big exception, because people want something solid before trusting it their money to it. We made up for our glitches by handling payment in person (Automated WhatsApp messages and bank account transfers, rather than shopping carts).

I still think that validation is #1 priority, because you'll probably have to build a dozen prototypes before you get to something people want. Our app with 1k users was ironically a low risk prototype. We were making a recipe app, but decided to test user behaviour by making a low carb variation first. Turned out that there's a lot more demand for low carb recipes than any recipes.