DEV Community

Ibrahim fonyuy
Ibrahim fonyuy

Posted on

NextPy, a Python-first full-stack web framework.

Over the past two years, I've been working on an open-source project called NextPy, a Python-first full-stack web framework.

The project started from a simple question:

«Why do Python developers often have to switch between Python for the backend and JavaScript/TypeScript for the frontend to build modern web applications?»

Rather than creating another backend framework, the goal has been to explore whether a modern full-stack developer experience can be achieved while staying primarily within the Python ecosystem.

Some of the features currently implemented include:

  • Python component system (PSX)
  • Server-Side Rendering (SSR)
  • Static Site Generation (SSG)
  • File-based routing
  • Reactive state management
  • Layouts and middleware
  • API routes
  • CLI tooling
  • Development server with hot reload
  • Authentication utilities
  • Static asset handling

One of the most interesting parts of the project has been building the rendering engine and component compiler. A significant amount of work has gone into making Python components feel declarative while still producing efficient HTML and JavaScript where needed.

There is still a lot to build and improve. Areas I'm actively working on include:

  • Performance optimization
  • Better developer tooling
  • Compiler improvements
  • Documentation
  • Testing
  • Ecosystem plugins

I'm looking for feedback from experienced Python developers and framework enthusiasts.

Some questions I'd genuinely like opinions on:

  • What features do you think are still missing from Python web frameworks?
  • What makes you choose Django, Flask, FastAPI, or another framework today?
  • If you were designing a modern Python-first web framework from scratch, what would you prioritize?

If you're interested in reviewing the project, suggesting improvements, or contributing, I'd really appreciate your feedback.

GitHub:
https://github.com/RahimStudios/nextpy-framework

Whether it's opening an issue, reviewing the architecture, improving documentation, or contributing code, every contribution is welcome.

I'm building this project in the open and would love to hear your thoughts.

Top comments (0)