Loading...
Answers
MenuIf you know for sure that your new iPhone app is going to miss the mark on a key feature should you launch it or wait?
We've gathered user feedback and we know we're missing the mark on a key feature. However, the app does provide some other useful features. Should we go ahead and launch it and accept the lesser reviews? Or, wait until we get it right? More specifically, it's a reservation app. You can make reservations but we aren't visually displaying the availability in a great way yet.
Answers
Simple answer. Wait. Happy to discuss this in more detail in a call if you feel that there might be circumstances beyond the actual user experience that might compel a pre-mature launch, but generally speaking, the app should be in a state of polish prior to app store review.
Use Hockey App or Enterprise Distribution to continue to get user feedback before launching to the app store.
I concur. You only have one chance to make a great first impression. If you have a marketing budget, you could seed the market with some teasers to build your email lists. But, otherwise, get the product polished then launch with fury.
Good luck. I am offering free calls to jest time clients. Send me a message and I will forward a link to you.
Kevin McCarthy
Www.kevinmccarthy.com
If the feature is at the core of the product (value proposition) then it needs to be dialed-in and working so that new users have a great experience.
You can still have it open to beta testers using TestFlight - that way your getting real feedback, but definitely iterate and get it working first.
Also, checkout www.usertesting.com to get fast video user testing completed on iOS apps - we order a video each week.
Launch. If it's successful that's great and you'll be adding an additional feature to it later on. If not you can still take it out of the store, wait for the new feature to be ready and republish it. BTW: adding a new feature to an app has never changed the download figures of my apps, it can change the user satisfaction or the number of stuff they buy in your app. I know it's a strange thing to say but it's a fact. Changing your marketing (keywords, icon, screenshots) is far more effective
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
-
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.RM
-
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.DM
-
What would be the cost to program an an app like Whatsapp? iOS only.
Well, the biggest cost here wouldn't be in the app, but in the server infrastructure. As usual with connected apps, people often forget they have to be connected to servers. The app itself is just a view to what the servers provide, so it's not the major cost. 20K $ to 100K $ should be enough. On server stuff, I expect it to be a lot more, particularly if you aim for a wide audience (several million $). On a Whatsapp clone, I'd consider: - solutions for performing calls through servers, not that easy. Look at what Twilio provides. WebRTC is an upcoming protocol that will ease that (web & mobile). - solutions for API, IM and user accounts management. Look at StackMob or Parse which are MBaaS (Mobile Backend as a Service). Hope it helps!AJ
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.