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
-
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!
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.
-
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. Mihai
-
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.
-
iOS App: Beta vs Launch Quietly?
I would suggest launching in a foreign app store only (ex: Canada). That will allow you to get more organic users to continue iterating without a big push. I got this idea from Matt Brezina (Founder of Sincerely, previously Xobni) https://clarity.fm/brezina - he's the man when it comes to testing & iterating mobile apps.