About Open Source Apps

Why this exists

Open-source app repositories are already available on GitHub.

But finding useful real app codebases is still not easy.

A developer often needs to know more than just the repository name and description:

• · Is this a real app or only a demo?
• · What stack does it use?
• · Which platforms does it support?
• · Is it actively maintained?
• · Is it mature or new?
• · Is it useful for learning?
• · Is it beginner-friendly or complex?
• · Does it have a clear license?
• · Are there similar apps worth checking?

A plain README list becomes hard to scan as the number of apps grows.

Open Source Apps turns that list into a structured directory.

What this project provides

Each app is organized with useful metadata, not just a link. The directory can show information such as:

• — App name and repository
• — Stack and language
• — Supported platforms
• — Category and tags
• — License
• — GitHub stars and forks
• — Activity status
• — Maturity level
• — Learning value
• — Contribution readiness
• — Caveats or missing information

This makes it easier to decide whether a repository is worth opening.

Why real app codebases matter

Small examples and tutorials are useful, but they do not show how real applications grow.

Real app codebases can show:

• Project structure
• Navigation patterns
• State management
• API integration
• Authentication
• Local storage
• Platform setup
• Build and release configuration
• Documentation and contribution practices

This project helps developers discover those real examples faster.

Why this list is still needed

A lot of developer attention right now is on AI coding tools. The pitch is familiar: describe the app, the model builds it, ship it.

This project does not pretend to compete with that. It does something different.

AI can generate code. It can also generate code that looks like an app, runs like an app, and breaks like an app.

A generated prototype is not the same as a real application. Real apps have structure that survives years of changes, decisions, edge cases, and contributors. They handle authentication, navigation, storage, releases, deprecation. They have bugs and they fix them.

That part does not come from prompting a model.

Open Source Apps is a list of those real applications. Curated by humans. Useful as a reference for:

• — Studying how a real app is structured
• — Comparing two real approaches to the same problem
• — Finding a codebase to learn from
• — Finding a codebase to contribute to
• — Finding a codebase to use as a reference when generating new code

AI tools are useful. A curated directory of real codebases is also useful. They are not the same thing, and one does not replace the other.

If you are using an AI tool to build something, you can also use this directory to find real apps to point it at. "Build me an app like this one" is a stronger instruction than "build me an app."

That is the idea.

What makes an app valuable here

Not every repository is useful in the same way.

• Mature and stable — Long-running, production-ish
• New and interesting — Recent, worth watching
• Good for studying architecture — Patterns worth reading
• Easier for beginners — Smaller, readable
• Useful but inactive — Stale, still a reference
• Archived but worth learning from — Patterns outlive the repo

The directory should make those differences visible.

Instead of treating every repository as the same, Open Source Apps adds context around each app.

Open data

The project is open-source by design.

The app data lives in the repository. The website is generated from static data. Metadata can be reviewed and improved through GitHub issues and pull requests.

This keeps the project simple, transparent, and community-maintainable.

Current focus

The first focus is mobile apps.

The original collection is Flutter-based, so Flutter is the strongest starting point. The directory is also designed to support other mobile stacks over time:

• Flutter — Original collection
• React Native — Second mobile stack
• Native iOS — Swift / SwiftUI
• Native Android — Kotlin / Compose
• Kotlin Multiplatform — Shared mobile + desktop
• Ionic & Capacitor — Web-tech mobile

Later, the same structure can support other app types such as desktop apps.