6 ms·
Hm, for some reason, you're viewing the old copy on the site. It was updated last night but I guess something happened and the changes didn't go through. I'll h
by iamjonlee 14y ago
Hm, for some reason, you're viewing the old copy on the site. It was updated last night but I guess something happened and the changes didn't go through. I'll have this updated shortly.
I get where you're going with this but we don't find the need to fully list out all features/functions at the point with a landing page. The purpose of the landing page was to obtain signups, which we're getting successfully. The issue is that all these people just want to wait for the stable version in the App Store. I had someone email me just 5 minutes ago telling me that he doesn't like betas because they crash. What do I say to that?
When we are ready to launch, we'll have a full site letting people know what we're about. We won't do it any earlier because there are some key features to making this app work but we don't want to disclose until we're almost ready to launch.
- aaronbrethorst 14y agoI'm not interested in feature lists, I'm saying that the core value prop of your product isn't clear to me from the landing page as I saw it. Crashy betas: Thank the user for their interest and promise to email them when the product's GA. Consumers tend not to be very technically savvy.