App Development Vocabulary — Day 15: Framework

Take everything from the last week. Routes, requests, responses, status codes, JSON, CRUD.

A framework ships with all of that wired up. You define a route, write the handler, and the framework takes care of receiving the HTTP request, running your code, and sending the response back with the right status code.

A backend framework (Express, Django, Rails) handles the server side. A frontend framework (React, Vue, Angular) handles screens and what happens when the user taps things.

The trade: you write less, and you write it the framework's way. Folder layout, naming, how data flows. Fighting those conventions is a bad time.

Quick check: Name one framework you've heard of, even if you're not sure what it does.

## SPOKEN LINES

Three months late, and your food delivery app still cannot take an order. You wrote your own request handling, your own routing, your own database layer, and every piece has a bug. Nobody who ships on time writes all of that from scratch.
- FRAMEWORK
- A framework is a pre-built structure you build your app inside. It handles the plumbing every app needs and gives you set places to put your own code. The framework is in charge, and it calls your code when it decides to.
- Rails and Django run the server side, React builds the screens, and Express handles routes in JavaScript.
- So a framework is a ready-made structure with rules for where your code goes. Tomorrow: Library, code you call instead of code that calls you.

## NEXT

Day 16: Library

0 comments

App Development Vocabulary — Day 15: Framework

CMD & Conquer

skool.com/cmdandconquer

Learn to run AI agents from the command line. No API costs, no dev team — just you and your terminal. In-house courses, private repos, live calls.

Leaderboard (30-day)