Our customers are the directors of organizations and on average communities pay us tens of thousands of $ each to put an app for their members in the store.
For example a university realizes that if they give an app to their students while they are still actively studying there, as alumni they will be part of a social network across the country where they can get job and business opportunities, date or just meet someone for an activity. They are more likely to donate and participate when the university posts their own events.
As for the users - you're right. A user doesn't necessarily want to have one app for each community. That's why the process should be seamless.
Ideally, an app should be usable across many communities. So think for example of Meetup.com as an app on our platform. It would be on the app store and you'd automatically see meetups across all the communities where you are a member.
For example a university realizes that if they give an app to their students while they are still actively studying there, as alumni they will be part of a social network across the country where they can get job and business opportunities, date or just meet someone for an activity. They are more likely to donate and participate when the university posts their own events.
As for the users - you're right. A user doesn't necessarily want to have one app for each community. That's why the process should be seamless.
Ideally, an app should be usable across many communities. So think for example of Meetup.com as an app on our platform. It would be on the app store and you'd automatically see meetups across all the communities where you are a member.
We go way further btw, with authentication and friend discovery: https://github.com/Qbix/auth
It has to be absolutely seamless, private and integrate with existing websites.