Loading...
Answers
MenuWhat is a good way to find a niche group of people, who already converse on a regular basis, to test my app?
It's early stage and I'd like to iterate using the feedback from small groups chatting around an interest they share.
Answers
Look on Google Communities for technology focused BETA testing groups...
Look on Linkedin Groups for business focused potential testers...
Look on Facebook Pages for people who like apps/companies like what you are trying to bring to market...
That should get you started.
It sounds like you want to get some feedback beyond just UX testing? If so, then your best bet is to find some customers - even better, some paying customers. Offer an introductory rate and keep the numbers small. The introductory rate could be free but better if you charge for it as you'll get a stronger qualification of the people giving feedback. You can get the initial group by being active where they spend time online, or build a community around their shared interests within appropriate platforms for the audience you're trying to target. Consider using paid ads as a quick way of getting the initial interest but don't promote the app directly - promote the shared interest first - if they engage with you, then they'll naturally move on to try the app. Within Facebook ads for example, you can easily target competitors / similar communities. Another way might also be to approach an existing app owner with an established community where you can naturally offer value to their audience but don't conflict or challenge what they offer - the owners/ team might also fall into the testing group and they can also tell you how they built their initial testing group before they launched...I hope this helps - cheers, Ben
I like Dan's answer, and I'd also suggest you check out:
- Other social sites like Twitter and Meetups.com
- Online community testing portal Ramen- https://ramen.is/
Above inviting individual people, you can give people an incentive to sharing your app within their community. i.e. Invite 5 people to unlock a level, connect your twitter to get more credits, etc.
Related Questions
-
What's your opinion on using something like usertesting.com vs. real time usability testing (online and offline)?
UserTesting can be instructive in terms of understanding whether people understand your copy, CTAs, and intended flows but generally, I've found the quality of their panels to be pretty low. You're almost always getting people who are not your actual users, so the feedback can only be generally applied as above. I find whatever web analytics package or packages you're using are generally able to provide much better insights. I also really do believe in *real* user panels. Buying pizza or offering small financial incentives to real users to click through new flows where they are talking out loud or answering specific questions is going to give far more actionable insights than anything else. What I like to do is take my best guesses as to what's not working or what I'm looking to improve and then discover/validate via real in-person customer panels. Happy to talk through this in more detail with you in a call.TW
-
What is the best way to find full stack mobile developers who are willing to work with me for equity, and what is fair compensation?
It's highly unlikely that you will be able to find competent full-stack mobile developers willing to work with you for equity, but if you do, "fair" compensation would be 50% or more of the equity in the Company. Approaching any developer with just an idea, diminishes your credibility as a potential co-founder. Here's why: If you're non-technical, you must show a "relentless resourcefulness" in moving your idea forward. This means finding the money necessary to get an MVP or even click-able prototype completed to show that while you might not be technical, you have the ability to raise money, and have enough product sense that you can articulate that into a prototype. If you can't raise or spend the relatively small amount of money required to successfully build a prototype, what evidence are you providing that developer that you are going to be able to create value for the business long-term? Full-stack mobile developers (although this is often quite a misnomer) are one of the most in-demand skill-sets of all Silicon Valley companies. That means that you're competing against established companies that can pay top dollar, and still provide meaningful equity incentives as well as recently funded startups who have further along the road in turning their idea into reality. I would suggest that you look at hiring contractors (I know of some great mobile dev shops that are reasonable) to build your first version. Expect to go solo at least until you have some form of early prototype. Then, you're in a much better position to attract a technical co-founder. Happy to talk you through any of this at any point.TW
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.comKM
-
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
-
How do I run a closed beta test for my mobile application? Development will be finished in 3 weeks.
You should try to engage people using social networks, it is easier to spread than email. The conversion rate on emails are low but is still a valid tool for that. Send and email with a simple and objective message that will make people want to try. The best way to have feedback from users is to watch them use the app. You should put them on the hands of everybody that you can and without any instrucions and just watch, don´t even say that the app is yours. Try to do it a lot. If you want feedback from others, you can include the feedback form inside the app and suggest users to answer occasionally. I would also strongly recommend to use a tool as Flurry Analytics. Is the best way to get data from how is the use of the application. Pay attention to those data and be open to change your app a lot, you may need more features or cut some off to make it easier to use. If you need more help please contact me.BS
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.