Problems with a Global app Object
Why a single module-level app limits you.
Problems with a Global app Object is a free Flask Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Flask Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
The Tempting Shortcut
Most tutorials create app at the top of a module and use it everywhere. It feels simple, but that single global object quietly limits how your project can grow. 🌱
One App, Forever
A module-level app is built the moment the file is imported. You get exactly one instance, with one fixed configuration, baked in for the whole process.
from flask import Flask
app = Flask(__name__) # created on importHard to Test
Testing wants a fresh app per run, ideally with test settings. A global app is already configured, so tests inherit your dev config and bleed state between them.
No Per-Environment Config
Dev, test, and prod each need different settings. With one global app, swapping config means editing globals or relying on import-time tricks that are easy to get wrong.
Circular Import Traps
Other modules import app to register routes, and app imports them back. This two-way dependency creates circular imports that crash on startup. 😣
Extensions Bound Too Early
Calling things like db = SQLAlchemy(app) at import time locks the extension to one app, before you even know which config to use.
db = SQLAlchemy(app) # bound too soonImport Order Becomes Fragile
Because everything hangs off one global, the import order starts to matter. Move one line and a route silently fails to register.
Multiple Apps Are Impossible
Sometimes you want two app instances, like one for an admin panel. A single global app makes running more than one in the same process awkward at best.
Config Set Before You Know It
At import time you often do not yet know if this is a test or prod run. A global app forces config decisions before that answer exists.
The Pattern That Fixes It
The cure is the application factory: a function that builds and returns a fresh, fully configured app on demand instead of one frozen global.
A Tiny Preview
Instead of a global, you call a function. Each call hands back a clean app you can configure however the situation needs.
def create_app():
app = Flask(__name__)
return appQuick Check
What is the core problem with a single module-level app object?
Recap
A global app is one frozen instance: hard to test, tough to configure per environment, and prone to circular imports. The factory pattern is the fix you will build next. 🚀
Frequently asked questions
Is the “Problems with a Global app Object” lesson free?
Yes — the full text of “Problems with a Global app Object” is free to read here on the web, and the Flask Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Flask Academy course, upgrade to CoddyKit PRO.
What will I learn in “Problems with a Global app Object”?
Why a single module-level app limits you. You practise Flask Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Flask Academy?
No prior experience is required. Flask Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Problems with a Global app Object” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Flask Academy lesson?
Yes. Every Flask Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Problems with a Global app Object
- Write a create_app Function
- Init Extensions with init_app
- Register Blueprints in the Factory