Skip to content

Latest commit

 

History

History
101 lines (75 loc) · 5.27 KB

from_demo_to_mvp.md

File metadata and controls

101 lines (75 loc) · 5.27 KB

From Demo to MVP 🚀

What to build in 🏗️

Can you build it using off-the-shelf software? It's highly likely you can. Some of the best at the moment:

More complex than that?

Build your MVP in Rails.

You already have a demo that you can port over. You know Rails. Your collaborators know Rails.

You're going to get a proper CTO to rebuild you a full JavaScript stack later anyway.

Testing 🧪

  • You didn't learn about testing during the Bootcamp. This is key. Have a watch of this Le Wagon lecture.

Rails Templates 👷

Check out awesome-rails-templates

Cool libraries 🤖

Cool gems 💎

Some great lists:

And some favourites:

Key Providers

Some great lists:

And some favourites:

Further resources 📝

FAQs

What features/design elements do most web apps have that we didn’t have during demo days? i.e. what takes it to looking and working like a real site?

  • As long as you have a core journey that fulfils your users’ jobs to be done, don't worry too much about this
  • Easy solution if you're worried about this is to buy a template for a few bucks
  • Remember you can improve this with usability testing later

Are there various benchmarks for web apps for things like number of pages, speed of load etc.?

  • Yes there are but as long as it’s not slowwww don't worry
  • Take a look at website-response-times if you're interested
  • The stats you should really care about are "are people visiting my site" and eventually "which parts". You can start with stuff like google analytics, or Mixpanel. This being said, if you have < 100 customers, talking to them is faster/easier

We didn’t touch questions like code scalability, production DB management, sourcing live data - are there tutorials/benchmarks for this?

  • Scale is really about "burn that bridge when it will be needed". It's not now, or probably the next two years. It's a nice problem to have that can be solved by throwing money at it (i.e. hire a senior dev)
  • Here's a resource on code scalability
  • Live data comes from APIs, scraping or building manually - make a call what you need

What about cybersecurity, customer data management (GDPR) etc.

  • Don't worry too much about cybersecurity for now but here are some general principles:
    • Keep dependencies updated
    • Ensure you use HTTPS
    • Don’t hardcode sensitive info
    • Encrypt user passwords
    • Avoid using raw SQL queries to prevent SQL injections
  • On GDPR, understand the principles and read this resource for startups

Are there a common list of gems that ruby apps will typically install?

  • Yes and here are some
  • General principle is to only use Gems when you need them
  • Remember they are also a dependency for your app