4 ms·
Why not determine pricing before they launched into beta or at least provide guidance numbers? The problem with the 30 day warning in pricing is that the exact
by throw_away 15y ago
Why not determine pricing before they launched into beta or at least provide guidance numbers? The problem with the 30 day warning in pricing is that the exact same thing that happened with gae pricing could happen here: someone builds a project with a certain price range in mind, pricing is announced and is far higher than expected for this use case, developer has 30 days to scramble to migrate their app and write angry blog posts.
Starting out as free is a mistake in my mind, because it doesn't properly set developer expectations from the start about what those price levels will be or even what metrics the price will be based upon. I would bet that no matter what they do, there will be some people who will be upset when pricing is finally announced.
- cmelbye 15y agoWell, I think for precisely those reasons, people will know not to form their own pricing expectations in their mind this time.