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?
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.
