Loading...
Answers
MenuI'm looking to sell one of my iOS apps. I don't know what to set the price at for buyers. What goes into setting the price?
The app is three years old. I have an iPad version, iPhone paid version, and an iPhone lite version. Last 12 months it's done $14,112 in sales. Since day one it's done $99k in just sales. I outsource all the work. Don't know exactly how much I've put into it, but it's a good amount.
Answers
Ultimately, it depends on the value the app has for the buyer (not how much money you put into developing it). Unfortunately there are many reasons for a buyer to purchase an app and so there are many ways to value an app (a multiple of yearly revenues,number of active users, etc.) . A good solution to this problem is to post your app on an auction site such as http://www.apptopia.com/ and let the marketplace give you an answer. Good luck with your sale.
Is it on a downward trend? What are the ongoing costs? This will help determine a break even price.
My first recommendation would be to go back and figure out how much you have spent on development, design, testing, services, fees, etc. No serious buyer is going to be interested in your app unless you can hand over a P&L statement giving accurate numbers for net profits. I put my own portfolio on the market back in April, and the first thing the broker asked for was the P&L statement for the last 12 months. If you've spent $87K and made $99K then most buyers will balk. But if you've spent $12K and made $99K then you've got a great profit margin, and even if the app has only made ~$1200/month for the last 12 months, it still has value because it will be inexpensive to maintain. Generally, you're looking at a valuation of 1.5-2x, as Vlad mentioned. And I agree with Ian that a large userbase or steady stream of installs will be enticing to a buyer even if your ARPU is low at the moment. Unless the app is ripe for reskinning (to Vlad's point) and you can convince a shrew businessperson that this garden is poised for exponential growth and it only needs more water, pruning, weeding, and fertilizer, then I'd say you're looking at $20K max. Apptopia isn't a bad place to start, though I'd recommend against spending the $140 for the "extra" exposure package.
Cheers,
Austin
Actually, the standard is past (4 months' revenue) x 9 but lately it has been going down.
However, your mainly selling your brand and users therefore it should never just a math problem.
Let me know if you want to further discuss with more details specific to your case.
Related Questions
-
If I am planning to launch a mobile app, do I need to register as a company before the launch?
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!AM
-
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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.