Guide: Deciding to Build on Flow

Context

We need a guide for people who are first considering building on Flow.

Existing Document:
Flow Primer, Github Repo and Playground to learn Flow and the smart contract language Cadence
Kitty Items example dapp demonstrating best practices for building on Flow.
Meet our community and get questions answered on our Discord and Forum
Sign up for updates at the bottom of the flow homepage

When people first learn about Flow in the context of a place to build a game, experience, or community they immediately have a number of questions that would ideally be answered by a short document they could skim, peruse more deeply, and/or share independently.
This document should live on docs.onflow.org - site hierarchy under construction

Definition of Done

This issue is intended to capture the work of making the resource that addresses the above areas and is very resource to follow-up/or kick off a conversation with someone who is deciding to build on Flow.

• A getting started guide for product/business folks to make decisions about building on Flow.
  Questions to answer:

• Why is this better than building somewhere else? What's uniquely possible here? Positioning/Messaging/Intro needed
• What does one mean when they say "build a blockchain experience" what should that include? Flow Product Matrix - coming soon
• Where do I start? TBC: Kitty Items

PR Review

Who is your Code Partner - algorithm/function check - Mickey, Brian
Who can provide external eyes - sanity check - Peter, Mackenzie

Internal Testing

Will share with people who are newly onboarding - they will be closest to the "newcomer decision maker" persona.
👀 requested include:
@noisygerman
@sideninja
@rafaelmorado and @jordankitty would also be great to get your perspective