HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
realworld-apps
realworld
TypeScript2017–2026
realworld-apps / realworld

realworld

"The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more

65Distinct people
72Mentions
0Explicit recommenders
84.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

"The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year72 dated mentions

Observed mentions: 2017-04-24 20:52:01 UTC to 2026-10-14 18:37:16 UTC.

051015202017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 7 submissions, 3 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 19 mentions; 7 submissions, 12 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1073
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1239
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC19712
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC12111
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC514
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC532
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
See how the exact same Medium.com clone is built using different frontends and backends You can combine any frontend with any backend, because they all adhere to the same API spec While most "todo" demos provide an excellent cursory glance at a framework's capabilities, they typically don't convey the knowledge required to actually build real applications with it — nor the real-world constraints a minimal demo never has to face. RealWorld solves this problem by providing the same demo app for each framework, at a sweet spot between simplicity and breadth. Join us on GitHub Discussions! 🎉 Implementations Over 100 implementations have been created using various languages, libraries, and frameworks. Explore them on CodebaseShow. Spec-compliant backends These backends pass the full API spec test suite: Nitro + Prisma + Zod — TypeScript Django Ninja — Python Create a new implementation Create a new implementation >>> Or you can view upcoming implementations (WIPs). Learn more Documentation introduction Every tutorial is built against the same API spec to ensure modularity of every frontend & backend A shared CSS theme is provided to build frontend implementations with identical UI/UX A shared E2E test suite is available to validate frontend implementations There is a hosted version of the backend API available for public usage at api.realworld.show, no API keys required — demo accounts are provided, and real accounts can't see each other There is an angular frontend plugged to this backend available at demo.realworld.show Interested in creating a new RealWorld stack? View our starter guide & spec Logo Attribution See LICENSES_LOGOS.md for framework logo licensing and attribution details. Active Maintainers c4ffein - Maintainer - maintains the spec, the test suites and the demo website Manuel Vila - Maintainer - creator of the Layr framework and the CodebaseShow website
Read the full README on GitHub

What Hacker News says

12 sources
This seems like a good example of productive discussion! While this won't necessarily solve the original poster's problems in of itself, it does give actionable steps on how to address them! As for anyone interested in real world comparisons of many of the popular frameworks (though not necessarily the most bleeding edge versions), feel free to have a look here: https://github.com/gothinkster/realworld The last time someone did a writeup on the results was in the March of 2020, but even then Angular wasn't necessarily that big in the bundle sizes that it generated: https://medium.com/dailyjs/a-realworld-comparison-of-front-e... Though the situation can indeed worsen as you introduce more and more libraries into the mix and as the project grows.
In Angular 11
> With a SPA framework, it could add it to the local list of emails and push to the server in the background, so it would transition instantly regardless of connectivity. With an SPA, it could be built to do this. But most SPAs aren't developed this way. Take a look at the "RealWorld" example SPA showcase (it's like a TodoMVC for SPAs), which has 43k stars on GitHub: https://github.com/gothinkster/realworld And go ahead and click on the demo site: https://demo.realworld.io/ In virtually every implementation, every time you change pages, the app re-downloads everything it needs for that route. Click on an article and then go back to the feed? Every time you will see a blank feed for about 500ms and only then do the articles stream in. You can say "well it doesn't have to be this way" or "this is just an example". But the reality is that it
Read the rest
usually is this way. This real world example is a good representation of how most SPAs are built, and they lack the type of functionality you're describing. They instead end up creating an experience that poorly emulates server side rendering, since now many page changes end up with a blank page or a loading indicator before the data arrives in a subsequent request. I don't know about you, but I'd rather wait 250ms once and then have the page arrive fully rendered over a transition that takes 2ms and then 200-400ms of multiple requests finishing and the page popping into place. The latter is really annoying, yet it's the experience most SPAs give you.
In DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
I don't believe in microbenchmarks like this anymore, I find more value in the typical rewrite experience reports (with the usual caveat of not placing any gains only on the language, but also on the fact that the domain problem is better known so even a rewrite in the same language would have provided some gains) There are different projects that allow people to compare languages in real scenarios: - Good old TodoMVC (http://todomvc.com/) - HNPWA (https://hnpwa.com/), that compares PWAs for accessing the HN api - RealWorld (https://github.com/gothinkster/realworld) that does the same but for both frontend and backend. The API between both is standardized, so you must be able to mix and match any frontend (including mobile) with any backend. The idea is to build a Medium clone, so it's much closer to a real use case than a todo list More
Read the rest
than the language, the framework and the architecture can play a role in speed. If I cared enough about relative performance, I'd build a client that adheres to the API spec of RealWorld and simulate a few thousand clients on a few thousands posts, all reading and writing posts and comments, and see how well they compare under load. That would be much more telling than comparing who can produce the nth Fibonacci number the fastest.
In Go vs. Crystal Performance
This seems dismissive. Books are great, but they're usually put together by a single, knowledgeable author, rarely demonstrate how to construct a full-stack application, and definitely don't lend themselves to consistently staying up-to-date. Something like the RealWorld repo [0], which shows how to put together something in a variety of different languages and styles, is better for this. [0] https://github.com/gothinkster/realworld
In Learn to code by creating working applications

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.