Hello,<p>we're planning to launch our app at the end of February. It's a mobile social network targeted to a specific niche. It's already in our plans to turn it into a marketplace as well, so users can buy and sell within the app.<p>Does it make sense in your opinion to first release the social part to build the community and then release all the marketplace function? Or it would be better to hold on till the marketplace is developed and then release the full app?<p>My idea is to release the social part and via press release, website and video teaser warn that there will be a marketplace soon.<p>Best,
Filippo<p>Sorry my english might not be perfect!
I think you should release the social version first, let it find it's audience and then introduce additional features (like marketplace). I would suggest this even if you had the 2nd part finished. Also, I would inform users, in advance, of the upcoming features. I`m not sure what this app is, but generally speaking "surprising" monetizing related features can create user backlash.
Be fair but not apologetic, show the value of your core product and of the upgrades to come.
I think the best solution is to release the first version and only scratch the surface about the marketplace. Do not directly hint about it. Maybe the early feedback of the first users will give you an idea of whether they want a marketplace in the first place or other major design/market directions you might want to follow to please them before spending time and money on something you're probably unsure will work.
I would release the social part first. I assume for the marketplace to work, you will need users. So I think it makes more sense to first generate a user base with the social part.<p>When you launch the marketplace, you could release it as a feature. It will show your users that you're actively developing the app and are trying to improve the user experience.