Loading...
Answers
MenuHave traction on iOS. People want Android app but we're bootstrapping and have no resources. Best way?
Answers
Ignore them and stay focused in growing your iOS community while proving out your CAC and engagement and retention numbers.
Small, resource-constrained teams need to absolutely *nail* one thing at a time.
Stay focused on the feedback from real, existing users not excuses from people who aren't using it.
While I agree with Tom, I think you might also try some crowd funding. Nothing confirms demand like users buying before it exists.
Use a video walk through of the iOS app to demonstrate the product, then reach out to the android community to see if it resonants with them. If it does they will pay. If it doesn't then be happy you didn't sink money into building it first.
I wouldn't even be considering the possibility at this point. You are still refining the product and figuring out how to engage+monetize. It is hard to "turn down" users, but splitting your focus will likely be a mistake until you've got the core figured out. More platforms is much more work than you will expect, especially with UI expectations being different.
You may not even need those options when it comes to growth either, depending on your space. Instragram did very well being extremely focused and waiting quite a while for other platforms.
Finally, when you do start acquiring users on other mobile platforms, be aware that they will convert at different rates! Don't depend on conversion behavior similar to iOS.
Related Questions
-
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
-
Looking for guidance for where I can find investors for my app?
As Ken suggested, there is a wide breadth of mobile offerings and although there are some great "mobile only" funds, each investor / fund has their own thesis that makes them interested in some but disinterested in others. Also, if your revenue generating, you should seriously consider bootstrapping further. Revenue is treated very strangely in early-stage investing and *might* work against you. AngelList is a great way to research investors but not effective in actually connecting with them. Find investors who you are confident will be passionate about what you're doing based on prior job experience or what you know they are investing in. Happy to talk in a call to help explain this further if you need more clarity.TW
-
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
-
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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.