How do you protect your idea when you hire a firm to build your app?

I've discussed ideas with hundreds of startups, I've been involved in about a dozen startups, my business is at $1M+ revenue. The bad news is, there is no good way to protect ideas. The good news is, in the vast majority of cases you don't really need to. If you're talking to people about your idea, you could ask them to sign an NDA ("Non Disclosure Agreement"), but NDAs are notoriously hard to enforce, and a lot of experienced startup people wouldn't sign them. For example, if you asked me to sign an NDA before we discussed your Idea, I'd tell you "thanks, but no thanks". This is probably the right place though to give the FriendDA an honorable mention: http://friendda.org/. Generally, I'd like to encourage you to share your Ideas freely. Even though telling people an idea is not completely without risk, generally the rewards from open discussions greatly outweigh the risks. Most startups fail because they build something nobody wants. Talking to people early, especially people who are the intended users/customers for your idea can be a great way to protect yourself from that risk, which is considerably higher than the risk of someone taking off with your idea. Another general note, is that while ideas matter, I would generally advise you to get into startup for which you can generate a lot of value beyond the idea. One indicator for a good match between a founder and a startup is the answer to the question: "why is that founder uniquely positioned to execute the idea well". The best way to protect yourself from competition is to build a product that other people would have a hard time building, even if they had 'the idea'. These are usually startups which contain lots of hard challenges on the way from the idea to the business, and if you can convincingly explain why you can probably solve those challenges while others would have a hard time, you're on the right path. If you have any further questions, I'd be happy to set up a call. Good luck.

You are right that the range is wide. You need to figure what are good values to have for your category. Also, you can focus on the trend (is your DAU/MAU increasing vs decreasing after you make changes) even if benchmarking is tough. Unless your app is adding a huge number of users every day (which can skew DAU/MAU), you can trust the ratio as a good indication of how engaged your users are. For games, DAU/MAU of ~20-30% is considered to be pretty good. For social apps, like a messenger app, a successful one would have a DAU/MAU closer to 50%. In general most apps struggle to get to DAU/MAU of 20% or more. Make sure you have the right definition of who is an active user for your app, and get a good sense of what % of users are actually using your app every day. Happy to discuss what is a good benchmark for your specific app depending on what it does.

On paper you have the advantage but after several startups control resides in he who knows how to execute the vision of the company.

I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!

There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. Mihai