Should I build the same project in multiple web frameworks?

Source: Dev.to

Overview

I’m planning a learning and portfolio experiment and would like opinions from anyone who has tried something similar.

Experiment Idea

• Build the exact same small project in multiple web frameworks (frontend and/or backend), keeping the features as identical as possible.
• The goal isn’t to master every framework, but to:
  • Understand the trade‑offs between them
  • See how opinionated each one is
  • Compare setup time, developer experience, and code complexity
  • Get better at spotting patterns that transfer between frameworks

Motivation

I feel this could be a good way to level up beyond just “learning one stack.”
The alternative is that it might become shallow learning compared to diving deep into a single framework.

Desired Project Characteristics

• Small but real
• Mostly CRUD
• Not too UI‑heavy
• Easy to keep consistent across frameworks

Possible Project Ideas

• A simple notes app
• A todo app with basic authentication
• A link shortener
• A minimal blog (posts + editor)

What I’d Like to Hear

If you’ve done something like this before, please share:

• What project you used
• How many frameworks you tried before it stopped being useful
• Whether it helped long‑term or just felt repetitive

Any advice is appreciated.