Loading...
Answers
MenuWhat are the best ways of studying my app users' habits?
My app has been in the App Store for 2 years and is top of its niche. We launched on Android 8 months ago and this is also going well. I want to take the app to the next level by learning from how my users (over 10k users per day) use the app. What do they press as soon as they open the app, why do they uninstall (or what were they doing right before uninstalling), how does a brand new user use the app (i.e. does he go straight to our tutorial or just dive in).
Any suggestions on SDKs, websites, etc . . that would help me to track down and study this information would be appreciated.
Answers
I would monitor the traffic on what app store your app is being downloaded to pinpoint frequency of downloads from individual markets, turnover rates from users, and ratings and comments which would contain valuable information from your users. Determining what previously provoked users to your product, what works what doesn't which such a large user base you should be able to derive a bunch of user data to be able to derive a methodology to further study habits of users and pinpoint at least some of the commonalities of good vs bad for your app.
To start you of look into Google Analytics, Fireball, Flurry, they are pretty sold for analytics of small to medium size traffic. All in all whatever method you use please take to account the current privacy issues now in your collection of data to avoid any future complications.
It's the wrong question. You should ask yourself: How do I want them to behave? And how do they want themselves to behave?
You should use MixPanel SDK and configure it to understand user behavior. Also use deep linking from Branch.io for deep linking.
With any mobile or web application you want to do one main thing:
Understand a user's journey through the app over time.
If you want the most professional and enterprise level of analytic information, i'd recommend a service called AppSee.
https://www.appsee.com/
From the time a user logs into the app, to the actions they take, to retargeting and understanding their future behaviors, I can help you out further if you have any questions.
Regards,
Matt McCullough
First, work on three different mock-ups of your next-generation app, each of which is focusing on a different aspect of your initial ideas.
Establish a small-but-effective-enough tester group having similar aspects with your target user and conduct an emprical research through in-depth interviews in three stages:
1. Before they start using the new app
2. During their initial experience with the app and/or after some use
3. After they become an expert user of the app
It sounds a very traditional method, but it always works great if you are prepared well with your early mockups and questions during the in-depth interviews.
Second stage of the research is the analysis of the findings which brings you lots of original and innovative potential ideas waiting to be implemented on your next generation products :))
Please always remember to include your users in your development process to make it more custom-tailored to their needs.
Thanks!
veyis
Firebase (Google Analytics) will help you to start. It has a feature where you can see how the user moves through your mobile app.
This can be very valuable on how your users use your app. You can also set up events to track any particular events in the mobile app.
In one of our apps, I used Google Analytics then (Firebase now) and found we had lots of users going to a screen on our app, I added some monetization and this helped increase revenue 25% overnight.
Looking at this data can be very helpful in taking you to the next level.
Cheers,
Mukul
PS - If you want help looking at the data or more tips, call me
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 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. MihaiMP
-
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
-
Pre-seed / seed funding for a community app... valuation and how much to take from investors?
To answer your questions: 1) Mobile companies at your stage usually raise angel funding at a valuation equivalent of $5,000,000 for US based companies and $4,000,000 to $4,500,000 for Canadian companies. 2) The valuation is a function of how much you raise against that valuation. For instance, selling $50,000 at $5,000,000 means you are selling debt that will convert into shares equal to roughly 1% of your company. 3) I would encourage you to check out my other answers that I've recently written that talk in detail about what to raise and when to raise. Given that you've now launched and your launch is "quiet", most seed investors are going to want to see substantial traction before investing. It's best for you to raise this money on a convertible note instead of actually selling equity, especially if you are intending on raising $50,000 - $100,000. Happy to schedule a call with you to provide more specifics and encourage you to read through the answers I've provided re fundraising advice to early-stage companies as well.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.