Loading...
Answers
MenuWhat is the generally agreed upon "good" DAU/MAU for mobile apps?
I've read articles, posts on Quora and others and the range is pretty wide. Would love everyones opinion.
Answers
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.
There is no one "good" DAU/MAU number, they vary a lot: is the app paid or free? Is it free with ads or free with IAPs (or maybe no monetization whatsoever)? Is it a game or something else? Some games/apps with low DAUs (in tens of thousands) make more money than much bigger competitors so you really need to focus on specifics of your app. Let me know if you can share more details of your app...
This is the wrong question to ask its like asking how much revenue is good. The more the better.
In general i would place a value of $.25 to $.75 in potential revenue on single MAU on average. However this varies based on the 3 levers which are: # of MAU, length of session, and frequency. It also varies on the type of monetization and app type ie in app purchase vs ads, games vs utilities. etc.
Another interesting thing we're seeing on apptopia now is people buying up android apps with large install base, but low engagement i.e. utilities. As it turns out you can monetize the apps with certain ad networks that install some addons to the phone and display ads outside the app or through push notification. Some examples: Pingjam for caller id ads, Airpush for push notification ads,StartApp and many more. At some point Google will catch up and block these networks but as of right now its a wild wild west out there....
hope this helps.
Daily Active Users (DAU) measures the number of active users who visit your app in a single day. Keep in mind this metric track usage based on individual, not sessions. For example, if a single user launches your app multiple times a day, the DAU for that user would still only be one. This gives you an accurate reading of how many unique visitors you are getting daily. Here is how you calculate DAU: # of users who open your app in a day. Monthly Active Users (MAU) measures the number of unique users to your app over a 30-day period. This stickiness metric indicates your app’s ability to attract and retain users over time.
In order to measure DAU/MAU, you’ll have to first identify what it means to be an active user for your app. Active users could do something as minimal as launching your app, or as significant as making a purchase or building a profile. While tracking DAU/MAU goes back to the dawn of user engagement, mobile marketers are advised to use this metric with caution. These numbers on their own do not provide an accurate assessment of growth. However, what DAU does not reveal is the number of users who download your app but never use it after the first launch, or those who get no value out of it and churn after a few days. So, while these numbers on their own can be classified as superficial vanity metrics, pairing them with meatier metrics that track conversions, revenue, and retention provide you with a more accurate reading of app growth.
A good DAU/MAU benchmark varies based on what type of app you have. Generally, you want to focus more on how your DAU/MAU is trending over time rather than the actual number. Apps over 20% are said to be good, and apps that reach 50%+ (like Facebook) are excellent.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What roles should the CEO and CTO have in a VC meeting?
The more important first impressions to leave a VC with are: 1) That you both are credible and inspire confidence that you can execute the plan you're fundraising on. 2) That there is good chemistry and a great relationship between the two of you; 3) That you can adequately address the concerns/objections/questions the VC raises. The CEO is expected to do most of the talking because the CEO should be the best person in the company at articulating the vision and value of the product and company you're building. If your CTO is comfortable presenting part of the pitch, it would be ideal for the CTO to speak to the product slides. The most important thing is for the CTO not to be a "bump on the log" meaning that you don't want them sitting there for most of the presentation with nothing to say. If you feel that's the case, you really shouldn't bring your CTO. Most VC meetings will not get technical and under the hood. Each question answered should be answered by the person best qualified to speak to that question. You should make eye-contact with your partner and use subtle body language to find a way to cue the other person to speak to that question or simply offer "CTO, would you like to answer that?" Bottom line, make sure that the CTO can speak confidently enough about the product and vision, otherwise -unless specifically asked by the VC - come alone. Fundraising is a big distraction to building and a good VC will always respect that in a first meeting, the CTO can be excused from attending in priority of building product. Happy to talk to you both on a call about helping get you feeling a bit more confident and prepared before your meeting. I was formerly a VC associate for a $500m fund and have raised money from VCs as a serial entrepreneur.Tom WilliamsTW
-
What happens to a convertible note if the company fails?
Convertible notes are by no means "earned." They are often easier to raise for early-stage companies who don't want to or can't raise an equity round. Equity rounds almost always require a simultaneous close of either the whole round or a defined "first close" representing a significant share of the raised amount. Where there are many participants in the round comprised mostly of small seed funds and/or angel investors, shepherding everyone to a closing date can be very difficult. If a company raises money on a note and the company fails, the investors are creditors, getting money back prior to any shareholder and any creditor that doesn't have security or statutory preference. In almost every case, convertible note holders in these situations would be lucky to get pennies back on the dollar. It would be highly unusual of / unheard of for a convertible note to come with personal guarantees. Happy to talk to you about the particulars of your situation and explain more to you based on what you're wanting to know.Tom WilliamsTW
-
What is the best technology for developing a new mobile app from scratch?
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. MihaiMihai PocorschiMP
-
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.Tom WilliamsTW
-
How much equity is typically taken by investors in a seed round?
From my experience I would not advise you to go with Venture Capital when you're a start-up as in the end they will most likely end up screwing you. A much better source for funding would be angel investors or friends/family. The question of how much equity should I give away differs for every start-up. I remember with my first company I gave away 30% because I wanted to get it off the ground. This was the best decision I ever made. Don't over valuate your company as having 70% of something is big is a whole lot better than having 100% of something small. You have to decide your companies value based on Assets/I.P(Intellectual Property)/Projections. I assume you have some follow up questions and I would love to help you so if you need any help feel free to call me. Kind Regards, GiulianoGiuliano SeneseGS
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.
