Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Startup WebDevelopment in 2013

Startup WebDevelopment in 2013

How to approach creating your own tech startup these days. Mindset, paradigm, technique and tools. Download the PDF to be able to click the links!

086c3227c1ff514187749985ee594523?s=128

Thomas Gorissen

March 23, 2013
Tweet

Transcript

  1. Startup WebDev in 2013 with a bit of . Thomas

    Gorissen
  2. None
  3. Welcome. Let’s build a web startup.

  4. Welcome. Let’s build a web startup. Easy peasy

  5. 1.

  6. None
  7. Envision your product.

  8. BIG Envision your product.

  9. BIG Envision your product. Put it in words, or maybe

    a video.
  10. None
  11. Make a 3 step plan to get there sustainably

  12. Make a 3 step plan to get there sustainably Caution:

    Will require use of spreadsheets. With numbers.
  13. None
  14. Make this plan and vision your daily prayer.

  15. Make this plan and vision your daily prayer. Amen

  16. 2.

  17. None
  18. Slash your vision to what you find necessary

  19. Slash your vision to what you find necessary Tschaka!

  20. None
  21. Then slash some more

  22. None
  23. Go get feedback

  24. None
  25. Slash it to the bare minimum

  26. None
  27. Create User Stories for the remains

  28. Create User Stories for the remains Describe the options for

    each interactor at every stage, what effect they have and where they lead to.
  29. Create User Stories for the remains Describe the options for

    each interactor at every stage, what effect they have and where they lead to. Put it in pictures.
  30. None
  31. Slash those User Stories to what really needs to be

    there.
  32. Slash those User Stories to what really needs to be

    there. Read also: Why scythes are underrated as a startup tool
  33. None
  34. You’ve successfully defined your first release.

  35. You’ve successfully defined your first release. Sweet

  36. 3.

  37. None
  38. Find your tools and platform

  39. None
  40. Native on mobile?

  41. Native on mobile? A: You need the AppStores for marketing

    B: You need specific low-level APIs or performance
  42. Native on mobile? A: You need the AppStores for marketing

    B: You need specific low-level APIs or performance Well, there’s also performance in HTML5...
  43. None
  44. In case of doubt: Use web standards!

  45. In case of doubt: Use web standards! Seriously!

  46. There were some pretty good talks from JSCamp.Asia about web

    standards:
  47. Meteor Backbone, LayoutManager, Ember Angular PhoneGap Cloud9 IDE Action.IO Grunt/Yeomen

    Jenkins Heroku Appfog AWS Softlayer CloudFlare Pivotal Tracker Podio Trello Google Drive Dropbox CodeKit Node Express MongoDB jQuery HTML5 Boilerplate Bootstrap Flight Hull Deployd Webflow Playground (soon) Must. use. git. These are just some tools I use, used, want to use or like
  48. 4.

  49. Grow fast little

  50. None
  51. Build small components with clear documented interfaces

  52. Build small components with clear documented interfaces There’s a talk

    for that:
  53. None
  54. In case of doubt: HTTP/REST/JSON all the things

  55. None
  56. ... or even JavaScript HTML and CSS

  57. ... or even JavaScript HTML and CSS There’s a talk

    for that:
  58. None
  59. Have small teams work on different components in parallel

  60. Have small teams work on different components in parallel If

    it needs more than 4 people, you’re doing it wrong
  61. None
  62. Test the critical path.

  63. Test the critical path. That’s usually what makes you money.

  64. None
  65. Release as often as you can

  66. Release as often as you can Rarely saw a user

    leave due to too frequent improvements...
  67. None
  68. Imagine.

  69. Imagine. Slash.

  70. Imagine. Slash. Build.

  71. Imagine. Slash. Build. Grow.

  72. Imagine. Slash. Build. Grow. Repeat.

  73. In between: Watch some videos!

  74. http://jscamp.asia

  75. Follow @serrynaimo @jscamp_asia