Loading...
Answers
MenuWhat is the best technical setup for our bootstrapped mhealth development team?
We are working in a private corporate git, with cto inviting key contract developers, using Dropbox for access to final design elements, testflight setup for beta testing... Should we be utilizing appcelerator or appgyver steroids to submit to app stores after beta testing? Or should our single source of code hosting be git? What are other high functioning bootstrapped tech teams doing?
Answers
We use github for code hosting, issue tracking system and specs ( the wiki portion ). Dropbox for large files like designs, videos. Basecamp for collaboration and discussion coupled with real time chats over hipchat.
I bought into the appcelerator promise a while back but had since abandoned it for native development. It depends on your app but our app would look and behave significantly worse had we not gone native.
Hope this helps, call me If you need more info.
I have over 6 years of experience handling software project teams who are "dispersed" and only communicate through "virtual" means and by that I mean over the internet or intranet. I still like to re-emphasize here that TECHNOLOGY should be only to support BUSINESS OJECTIVES and not the other way round. This question borders on what ENTERPRISE ARCHITECTURE framework you and your CTO have determined for this project. Your enterprise architecture should be such that it is framed upon architecture "principles" that would enable your business or project objectives. Any of those app development tools you mentioned like Appcelerator ro appyver should do your job but then you need to ask yourself 'does it make more an ECONOMIC sense to DUPICATE tools and processes than to have a CONSOLIDATED tool that can be shared across our enterprise?' When you answer that question rightly, then you should be able to SELECT the right TOOL for your PROJECT NEED(Forgive my capitalization, it is meant for hinting).
In my experience as an enterprise architect, having a single consolidated master data repository is usually the optimal way to go.
Your other "high functioning bootstrapped tech teams" might be handling the other activities in the App development workflow such as Desinging, Development, Coding, Debugging, etc. depending on how the project manager decomposed the work packages.
You can give me a call for more clarifications.
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
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.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
-
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
-
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.