There's mention of rear-facing jump seats as an option, that probably gets you 2 in front and 5 in back but the 5 in back probably only works well if they are children.
I think the big advantage here is reducing the noise and the effort. If I'm going mountain biking this afternoon it only takes me about 10 seconds to let all my mountain biking buddies know that. I don't have to figure out which group I'm sending the invitation to and explain what I'm going to do and where.
I built the backend server with Rails (I knew this already), but the rest was native iOS, so all Xcode. As far as how to architect it, I'm not sure I'd be much help. I basically jotted down what the app would look like and just started with individual features. I did have some help and advice from two iOS devs when it came to questions like, "I want it to do X, what is that called in the iOS world?", so I was better able to search for answers.
Basically, I'd just start with a feature of your app and try to build it. Most likely, someone smarter than both of us has done it and written about it (or at least something similar enough). Once you start writing code, you'll quickly get a feel for how things work and have a better sense of what the overall app should look like. Not sure if that helps any but good luck.
I built this in 37 days with no prior iOS experience (though I did have experience with ruby/rails). I think it could be useful but I'd love some feedback.
Instead requiring all of your friends install the app why not have people add friends by email/cell number. Then on the backend determine if they have an account if they have an account send it through the app otherwise they can just send an email/sms.
However, this idea eliminates the risk that your uers won't bug each of their friends to install your app.
Also, the right design for the email notification can act as great marketing for your app. You can certainly make a better landing page on your website than your app's product page in the App Store.
I think most of us would love to give feedback, but at first glance it seems requires all the "friends" to use the same paid app is not something easy to tag along.
Besides, I am using Android now ;-) so...
Just a side note, for solutions that needs social networking to work, it would be extremely hard to charge people up front. You gonna have to give it away for free (first) to earn some viral effects to kick in.
This is a good point and I see the turn off of "pay for this and hope your friends will too." This is the sort of feedback I was looking for - would someone buy this then ask their friends to do the same or is that too much to ask?
I don't think so. If I tell my friends "hey this app is cool, we should all buy it" I think that could work. It's only $2, you spend way more than that doing most anything with friends anyway.
I would consider some sort of free version of this app, so people can join without risk. Maybe make a version that limits you to 3 friends for free, or unlimited friends for $1.99?
Yeah, combined with the above comment, I think this is a good idea. This was actually my initial thought (but with 2 friends) early on, but I wanted to experiment with the idea of only having a paid version because I believe paid apps get more usage (I might be crazy here).
From my experience free trumps paid unless the paid app is promoted by apple/lots of blogs. You may get more return users with a paid app (since they shelled out the cash they will probably want to get their money's worth) but if you're trying to build a user base and especially if your app relies on one, which yours seems to, free is the way to go.
I agree. Sounds like a great app, but to be useful, I have to pay for it and so do each of my friends (unless you add the email / SMS feature suggested above).
I suggest a fremium pricing model. Perhaps all features are free exept one killer feature, which is an optional in-app purchase. For example - push notifications when one of your friends suggests an activity.
As a current Buildium user, I really like the look of this. I'm a small property manager and although I love the convenience of having software like this available I'm curious how your online payments are processed. My biggest complaint with my current program is that it takes 5-7 days for rents to hit my account and then another 5-7 for them to hit the owners' accounts.
I think a great market for a product like this would be real estate agents that do some property management (10-25 units).
Thank you for asking this. I am in a very similar position and just recently threw myself out there for a rails job. After showing off some small and simple projects I've done, I was told that I need to learn more (specifically: TDD). So, I'm reading and trying out everything I can and will repeat the process.