We started late September, when we were annoyed that such an app didn't exist, and so decided to make one ourselves.

To address all the things that you mentioned in your comment:

• We tried it on an HTC Inspire, HTC EVO, and two others (don't remember exactly what models) and the compass kept getting interference and was very twitchy. Like I mentioned before, I'm sure there are other phones that have good compasses, but our sample data told us that we should go with the system where we don't have to worry about hardware.

• When we started, Android already had a bigger market share

• Sounds like you're suggesting that we should have limited our Android app to only some Android phones. I don't think people in the Android community would be happy about that. We tried different methods of working around that - such as using the direction of movement of the user instead of the compass - but none worked well. Maybe you're just a much better programmer than us (a very real possibility, considering how none of us are professional programmers). But we couldn't come up with a way to take in incorrect data and make it correct without a second reference point. If you do know how to do this (and I mean specifically, not "adding an 'if' statement or two"), we'd appreciate it if you could let us know so that we can include it in the Android app.

• There's really no one "in charge" of this project as we're equal three co-founders. But I'm the one who started it and who made the final decision to go with the iPhone, so I guess you can direct your criticism at me. No, I wasn't concerned about "coding something cool". I was annoyed that something like this didn't exist, and didn't like how other people had attempted it before, so I figured we'd do it ourselves and do it better.

• I'm not sure what you mean by " flashy compass features ". We have a back-end that supports maps created by users, and allows them to share and download them, which is what we use to overcome the issue of temporary destinations such as stages in a music festival (or where you parked your car), or unmarked ones such as places on a hiking trail. It's a big part of our app. You should check it out if you get the chance.

• I'm sorry to hear you find it useless. We've had a lot of feedback from people who've loved it and found it useful, so if you have any suggestions on how to improve what we have (besides switching to Android :) ), we'd be happy to hear them.

• I have to make something clear: This is NOT a "Coachella app". This is a navigation app. We are directing it at Coachella people right now because that's a place where it would be very useful, and cause all three of us are big fans of the show and are going there. This is something that can be used by anyone, at any place, and not just Coachella.

• To add to my point above: We are not contracted by Goldenvoice, and we are not a Coachella app. We are not payed by anyone, and have made absolutely no money on this project. This isn't some conspiracy to keep Android users out of the market. We are three friends who decided to make something that we ourselves would like to use. Along the way, we were met with a lot of enthusiasm, so the project got bigger and more ambitious. If you have complaints about Goldenvoice, send them an email. We are not in anyway connected to them.

• In the end, even though I feel like you misunderstood our intentions, I still appreciate you taking the time to write out your issues and frustrations about the app. Any feedback is always better than no feedback. If you have any more questions or comments, please feel free to voice them here, or at our contact email.

Thanks,

Ali