Read This Or Get Confused

The Final Boss Appeared!

The Most Skipped Section Of Every Course

Stop Watching If You Lack These 2 Things

Why Do You Need A Workflow?

Trigger Warning

What's The Plan?

Step 1 - The Role

Step 2 - The Wish

Step 3 - The PRD

Step 4 - The Phase 1

Step 5 - The User Journey

Step 6 - The Politically Incorrect Sorting

Step 7 - The UI Development Plan

Step 8 - The Vibe

Step 9 - The UI Flow

Step 10 - The Design System

Step 11 - The Storage

Introduction

Know Exactly What To Build Before You Write A Single Line

Create a masterplan that contains all the information you'll need to start building a beautiful and professional application for yourself or your clients.
        In just 30 minutes you'll know what features you'll need, which screens, how to navigate them, and even how your database tables should look like

30-Minute Fullstack Masterplan

The document that has saved freelancers thousands upon thousands from greedy clients

The workflow that allows you to build and deliver apps that cost 4-5 figures in just a few days

My 11-step process for generating everything you need before you code a single line

The (now) politically incorrect way to sort your features

The colors, borders, shadows and every other detail you'll need for your front end

How to pre-plan what all your screens should look like structurally

How to generate all the tables you'll need for the next year

 Step 11 is the storage. So we have a great plan for the front end client already.

But we also need to think about the backend as unsexy as it might be for some. This final part is going to help us come up with great schema for our specific cup and our specific circumstance circumstances, so we don't go ahead and build something that's ultimately unscalable and it will so that we don't have to potentially make massivechanges to our databases and schemas and.

End up with basically huge problem because the further down the layers you are, the more complex, the more complicated and hard it is to change something as you scale up. So the database might be the hardest to change, then the backend and then the front end.

So with that being said, here is our prompt. This is obviously going to need the backend and since it's bolt I'm going have to use Supabase with it. Give me the most scalable and price efficient schemas I need to use for this app with Supabase because if we don't create the schemas ourselves, bolt will try to do it in the way that he thinks is best, but.

Bolt also doesn't really take account scalability and price efficiency. So while it will give you a great schema, it might not be the best one to use long term.

---
title: Step 11 - The Storage
isPublicLesson: true
privateVideoUrl: https://stream.mux.com/AGt6tgjaIqX3N5GID4dRC6tExxnYshqX301601lSYlIsk.m3u8
---

 Step 11 is the storage. So we have a great plan for the front end client already.

But we also need to think about the backend as unsexy as it might be for some. This final part is going to help us come up with great schema for our specific cup and our specific circumstance circumstances, so we don't go ahead and build something that's ultimately unscalable and it will so that we don't have to potentially make massivechanges to our databases and schemas and.

End up with basically huge problem because the further down the layers you are, the more complex, the more complicated and hard it is to change something as you scale up. So the database might be the hardest to change, then the backend and then the front end.

So with that being said, here is our prompt. This is obviously going to need the backend and since it's bolt I'm going have to use Supabase with it. Give me the most scalable and price efficient schemas I need to use for this app with Supabase because if we don't create the schemas ourselves, bolt will try to do it in the way that he thinks is best, but.

GC Tsalamagkakis

So we have a great plan for the front end client already.

But we also need to think about the backend,

This file part is going to help us come up

And I was so that we does have to potentially make

Because the further down the layers you are,

the more complex, the more complicated and hard it is

So the database might be the hardest change

So with that being said, here is our prompt.

This is obviously going to need a backend

I'm going to have to use super-based with it.

Give me the most available and price efficient schema

I need to use for this app with super-based.

Because if we don't create the schema as more ourselves,

bulk will try to do it in a way that it thinks it's best,

but bulk also doesn't really take account scalability

They might not be the best to enter you long term.

optimized for all the security in queries,

some setup nodes are in less than a blown up tables,

all the session you guys will do for our patience for our

and super-based account position for data limits

That is really to have the maximum journal entries,

but it's good that it's taking about more than just up building.

Which was obviously wouldn't do it by themselves.

I'd love to cover everything today, honestly,

but it's already been 45 minutes since we started.

And there's not enough time to do everything.