Tech 4 Non-Techies
Dos and Don’ts for Developing Your App
10 practical tips
for testing your
app concept
Based on our experience...
Building software for a variety of clients:
Enterprise platforms e.g. Dividend Finance,
McKinsey, Standard Textile
Non-profits e.g. Teach For America, Imagine
H20
~60 startups across various industries
Doing this without coding, as MBAs without
technical backgrounds
(1) Before the build
Do:
Work in a space you have intimate knowledge of, and passion for
Don’t:
Pursue a clever idea for a “this for that”
(1) Before the build
Do:
Commit to iterations with fixed timeline and budget
Don’t:
Commit to a single product vision
(1) Before the build
Do:
Spend time developing the few first customers first
Don’t:
Be everything to everyone
(2) Scoping your app
Do:
Plan the Data and Flow objects - just like you describe things it in real life
Don’t:
Start with small picture e.g. one page and work backward
(2) Scoping your app
Do:
Build Wireframes
Don’t:
Build Mockups
(2) Scoping your app
Do:
Research existing sites
Don’t:
Think from scratch
(3) Design and build
Do:
Build Responsive Web Apps
Don’t:
Build Native Apps from the start
(3) Design and build
Do:
Leverage external services (e.g. email/SMS, customer support, payment,
artificial intelligence)
Don’t:
Build it all from scratch
(3) Design and build
Do:
Limit yourself to 3 colors, 3 font formats, and equal spacing/padding
Don’t:
Get creative with formatting
(3) Design and build
Do:
“Build for Granny”: minimize clickable elements, create a single flow
Don’t:
Overload users with information exceeding their attention span
Useful No-Code Resources
Making wireframes - myBalsamiq
Design guidelines - Google Material Design
Building apps without code - Bubble
Integrating with services - Zapier, Blockspring, RapidAPI
Also check out:
Startup Stash - a good list of tools to use across all mvp aspects
Thank You
Questions ?

Dos and Don'ts for Developing Your App

  • 1.
    Tech 4 Non-Techies Dosand Don’ts for Developing Your App
  • 2.
    10 practical tips fortesting your app concept Based on our experience... Building software for a variety of clients: Enterprise platforms e.g. Dividend Finance, McKinsey, Standard Textile Non-profits e.g. Teach For America, Imagine H20 ~60 startups across various industries Doing this without coding, as MBAs without technical backgrounds
  • 3.
    (1) Before thebuild Do: Work in a space you have intimate knowledge of, and passion for Don’t: Pursue a clever idea for a “this for that”
  • 4.
    (1) Before thebuild Do: Commit to iterations with fixed timeline and budget Don’t: Commit to a single product vision
  • 5.
    (1) Before thebuild Do: Spend time developing the few first customers first Don’t: Be everything to everyone
  • 6.
    (2) Scoping yourapp Do: Plan the Data and Flow objects - just like you describe things it in real life Don’t: Start with small picture e.g. one page and work backward
  • 7.
    (2) Scoping yourapp Do: Build Wireframes Don’t: Build Mockups
  • 8.
    (2) Scoping yourapp Do: Research existing sites Don’t: Think from scratch
  • 9.
    (3) Design andbuild Do: Build Responsive Web Apps Don’t: Build Native Apps from the start
  • 10.
    (3) Design andbuild Do: Leverage external services (e.g. email/SMS, customer support, payment, artificial intelligence) Don’t: Build it all from scratch
  • 11.
    (3) Design andbuild Do: Limit yourself to 3 colors, 3 font formats, and equal spacing/padding Don’t: Get creative with formatting
  • 12.
    (3) Design andbuild Do: “Build for Granny”: minimize clickable elements, create a single flow Don’t: Overload users with information exceeding their attention span
  • 13.
    Useful No-Code Resources Makingwireframes - myBalsamiq Design guidelines - Google Material Design Building apps without code - Bubble Integrating with services - Zapier, Blockspring, RapidAPI Also check out: Startup Stash - a good list of tools to use across all mvp aspects
  • 14.

Editor's Notes

  • #4 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts
  • #5 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts
  • #6 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts
  • #7 Illustrate with example of a two-sided marketplace You wouldn’t go on a vacation by planning the trip after reaching the destination.
  • #8 It’s more important to decide which buttons to have than deciding what size & color should they be. No good business lost customers because it didn’t have the perfect colors in early stages
  • #9 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts Example: If building an ecommerce store, simply check out amazon, shopify and ebay
  • #10 Responsive is one size fits all. Native is when the graphics, gestures and UI is the most important factor in your app
  • #11 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts
  • #12 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts
  • #13 Don’t reinvent the wheel. Popular apps have mentally trained users to ‘behave’ in a certain way / ‘expect’ layouts