3 ms·

I'll provide my two cents, in the case of group activities. It seems awfully convenient to have a single site (e.g., meetup) for, say, if I'm traveling to a new

I'll provide my two cents, in the case of group activities. It seems awfully convenient to have a single site (e.g., meetup) for, say, if I'm traveling to a new city and looking for something to do. It'd seem like an unnecessary barrier to entry to have to find the locally hosted instance of every particular problem, every location I go. Knowing I can use Yelp or Groupon etc to find local restaurants or deals anywhere is actually pretty helpful. To get to the core of your premise: > I thought there was no reason that signals needed to go through server farms in California just to organize a local dinner, have a local marketplace, classes, dating, or a host of other things. You might think there is no reason for this; but users of these services aren't concerned with this problem. If your selling point is "Hey, don't you hate how this one big corporation has a monopoly on <marketplace> <group activities> etc?", you're going to hear crickets. This isn't a customer problem.

EGreg 9y ago
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. We go way further btw, with authentication and friend discovery: https://github.com/Qbix/auth https://github.com/Qbix/auth It has to be absolutely seamless, private and integrate with existing websites.

EGreg 9y ago

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. We go way further btw, with authentication and friend discovery: https://github.com/Qbix/auth https://github.com/Qbix/auth It has to be absolutely seamless, private and integrate with existing websites.