How to Survive in a Startup Accelerator as a Technical Co-Founder
Download as KEY, PDF2 likes609 views
- The document provides advice for technical co-founders in a startup accelerator on how to survive the 90 day program, including focusing on your product over everything else, the debate around native vs. HTML5 development, and the importance of user experience/design even for Facebook. - It emphasizes focusing only on your product, not getting distracted by mentors or other opportunities, and the risks of launching too quickly without proper testing versus launching at a conference with time left for fixes.
How to Survive in a Startup Accelerator as a Technical Co-Founder
- 1. HOW TO SURVIVE IN A STARTUP ACCELERATOR AS A TECHNICAL CO-FOUNDER @JustinMcCammon #SoCalCodeCamp #BestTalkEver #Justin4President #Hashtags
- 2. Developer User Experience (UX) Strategy Mobile ME IN 60 SECONDS
- 3. GONNABE
- 6. 90 Days $20k Office Space Mentorship Demo Day START ENGINE
- 7. HTML 5 VS NATIVE
- 8. ++ Fast(er) Development Cycle Deploy across platforms (maybe) CSS Hardware Acceleration (3d transforms) Lots of talent available
- 9. -- Debugging in XCode Poor JS Performance in UIWebView At the mercy of Apple “Web Standards”
- 10. ++ Native performance Hardware APIs More stable environment
- 11. -- Lack of / expensive talent Slower development cycle Platform specific
- 12. THE GAPS IN PHONEGAP
- 14. MENTOR WHIPLASH
- 15. Your product. Everything else. FOCUS
- 16. Your product. Everything else. NO SERIOUSLY, FOCUS
- 17. THERE’S NO CODING IN THE CHAMPAGNE ROOM
- 18. WHO THE #&@! NEEDS UX OR DESIGN?
- 19. “The biggest thing that’s different is that Facebook is not about human- computer interaction.” -Chris Cox (VP of Product at FB) (in the past 3 years Facebook’s design team has grown from 20 to 90)
- 22. STEALTH MODE IS FOR LOSERS
- 23. HOW TO MINIFY YOUR SOCIAL LIFE WITHOUT DROPPING THE FRIENDS TABLE
- 24. LAUNCHING
- 25. 1. Launch at a big conference 2. Cut your dev time by 1/3 3. Cut out time for testing 4. Tell everyone 5. Leave zero time for fixes DOING IT WRONG
- 26. 1. Launch quietly (and early) 2. Test 3. Test some more 4. Leave time to get it stable DOING IT RIGHT
- 27. DAY 91
- 28. @JustinMcCammon bit.ly/survivecodecamp THANK YOU