Loading...
Answers
MenuHow do you protect your idea when you hire a firm to build your app?
This question has no further details.
Answers
The standard procedure is to sign a mutual non-disclosure agreement with whoever you are disclosing your idea to, before you hire the firm.
Once your product is built or is in the process, you have the option to patent or copyright it.
Here's my article that gives the complete details on both: http://thenextweb.com/insider/2015/05/07/does-your-mobile-app-need-a-patent/
We often deal with that type of question over at LawTrades.
You should build trust with the firm... and then making them sign all the proper legal documents.
Stuff like non-disclosure agreements, non-compete agreements, and intellectual property assignment agreement come to mind.
Happy to learn more about your needs and give you a tailored response for protecting your idea.
The simple answer is contracts and choosing your partner well.
The long answer is more complicated. Is there anything about your app idea that is ownable defendable? Would your partner have to develop or leverage existing IP or technology in order to bring your app to market? Is there any similar competitors already in the market?
The reality is that most app developers or firms are more interested in building apps than stealing other people's ideas. Their business is app development and deployment—not managing, marketing and running a business like yours. With that being said, there are dubious people out there doing sneaky things.
Find a developer or firm with a good reputation and track record. Engage with them professionally, put the appropriate contracts and paperwork in place, and move forward. If your idea can be patented do that. But keep in mind, that many firms may have to develop code or applications to make your app a reality and depending on your contracts, that work may end up being their IP—which is not an uncommon practice.
Hope that helps, feel free to reach out if you have any other questions.
Related Questions
-
What tools to use for mobile Prototyping ?
My 2 favourite are: - www.uxpin.com - www.flinto.com Flinto is by far my favorite for mobile. I also us www.balsamiq.com for anything wireframe. Sometimes I jump into Sketch http://www.bohemiancoding.com/sketch/ for more high fidelity mockups using their Mirror feature http://www.bohemiancoding.com/sketch/mirror/ Hope that helps. P.S. There's a tonne of Mobile UX experts on Clarity, many $1/min - call them, you'll learn so much. my2cents.DM
-
What is the generally agreed upon "good" DAU/MAU for mobile apps?
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.SG
-
If I have 51 percent and my partner has 49 percent of our company, what real decision making authority would I have?
On paper you have the advantage but after several startups control resides in he who knows how to execute the vision of the company.HJ
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.