Loading...
Answers
MenuWhat is the best way to start with mobile considering that I don't have have programming background? (only html and basic CSS) ?
I'm thinking on developing an app for cognitive behavioral therapy for insomniacs. I have a full-time job so I don't have much time. I would like to prove that my idea works without spending a lot of time. My focus will be prototyping, testing and doing UX/Usability tests keep improving the app. What is the easiest way to start? I've found this: http://www.siberiancms.com/ but I'm not sure if that's good. Should I focus on Android because the approval process is easier? I see two main functions in this app, data collection from patients so the psychologist can keep track of his patients and also education for the patients. I might get some help from a freelancer but I want to be part of the architecture process so I can learn too.
Answers
I admire your ambition but I really do need to caution you against learning to code as a means of building out your app. If you want to do this as a fun hobby to teach yourself to code, then by all means do it but if you seriously want to build and launch an app that you think has a potential commercial appeal, then you need to do it in a way that maximizes your chance of success.
I'm happy to refer to you reasonable mobile development shops that do excellent work. You should budget a *minimum* of $25,000 USD to build a single platform app that is fully functioning and launch-ready and another at least $25,000 in reserve for paid user acquisition.
If you can't invest $50,000 or find friends, family or strangers willing to support this pursuit financially, I'd argue that you'll be wasting your time.
Happy to talk to you in more detail in a call.
The main question to be asking yourself is this an app that people really want or need. I have been working in healthcare for over 20 years and I can tell you that on the surface it seems like a good idea.
My suggestion is to first get a conversation started regarding your product then make sure that you are offering specifically what the market demands. You can do this be participating in LinkedIn groups, etc.
Finally, I work with a lot of programmers and startups and suggest that you look around for places to outsource the work. I will not give any lists of places here, but I will tell you that prices vary from one place to another.
By the time you become a programmer the timing for your app may have passed and the demand may have been filled. Start learning, but don't count on doing the work yourself.
Don't Stop and Take Massive Action.
Regards,
Michael T. Irvin
www.michaelirvin.net
My books are now available on Amazon.com by searching for books by Michael T. Irvin
First, that sounds like a promising idea for an app.
To give you some idea of my background, I'm a professional programmer and also founded a website that managed the outsourcing process for over 300,000 programmers. Testing and usability tests are great things for a non-technical founder to be doing. However, you really should not be doing the architecture. It would be like if I wanted to run a company to design bridges, and told the engineer that I was going to share architecture duties with him. I just don't have the expertise, and it's not something that can just be picked up in a matter of months.
Here's my advice for you. There must be some reason why you are thinking that you want to be involved in the architecture. I'd recommend examining those reasons, and finding out if there is another way to accomplish your goal. If you want to discuss further, feel free to hit me up, here on Clarity. Good luck with your endeavor.
Do you expect to run a business with this app ?
If yes, fill a leancanvas (on paper or http://www.leanstack.com/), validate your assumptions with interviews of patients and psychologists, show them mockups of the app with uxpin or balsamiq. When it's validated that you can earn money (how much are they willing to pay, how many are they), outsource the development.
If no, find a student to get the job done or if the app is not very complicated, learn to do it yourself with mobile app builders (http://mashable.com/2013/12/03/build-mobile-apps/).
If you need more advice, feel free to have a free call with me https://clarity.fm/laurentroger/white665or on www.sohelpful.me/laurentroger
Related Questions
-
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
-
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
-
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 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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.