Loosebird

About the Project

Why the name Loosebird?

Vogel im Käfig is a German metaphor that means "bird in a cage." It represents someone who has the potential to be free but is trapped by external or internal circumstances. Billions of users today are metaphorically "locked" into proprietary software, web-based applications, closed systems, and restrictive architectures — like birds in a cage.

The name Loosebird embodies our mission: to set those birds free. We provide open-source, native, and universal alternatives that give users back control over their own digital lives.

Why are all your applications named after birds?

Because it’s fun. Birds evoke freedom, lightness, and speed.

What does "native software" actually mean, and why does it matter?

Native software is built specifically for a given operating system using its recommended toolkits and APIs (e.g., GTK, Qt, WinUI, SwiftUI). It does not rely on web technologies wrapped in a browser shell (like Electron).

Why it matters:

• Performance: Lower memory and CPU usage, faster startup times.
• Integration: Feels like a natural part of the system, respecting dark/light modes, accessibility features, and familiar shortcuts.
• Sustainability: Extends hardware lifespan by not wasting resources.
• Offline-first mindset: Native applications do not assume the cloud is always available.

We believe that giving you a fast, focused tool is a form of respect.

Why do you give everything away for free?

We distinguish between two concepts of "free":

• Free as in freedom — you can use, study, modify, and share our software.
• Free as in community-supported — the zero price tag is made possible by people who believe in the mission.

Our work is sustained by donations and volunteer contributions. We want high-quality tools to be a right, not a luxury gated by subscriptions.

Do you take political stances or engage in social issues?

Loosebird is a software organization. Our only mission is building native, open‑source tools that respect user freedom. We do not involve ourselves in wars, political movements, activism, or any agenda outside the scope of software development.

This is not indifference — it is a deliberate choice of focus. We believe that only a strictly neutral, centered approach can create a safe, inclusive space where anyone, regardless of background, can collaborate on code without distraction. We leave external battles to others. Our fight is for software sovereignty, not for ideological territory.

All our software is neutral and centered by design. The tools do not push views, promote causes, or embed opinions. They do one job, and they do it cleanly.

Technology & Stack

What is your tech stack and why did you choose it?

We use a custom stack designed for clarity, performance, and native output:

• Slint – a modern, declarative language for building native user interfaces. It is fast, professional, and compiles to efficient machine code.
• Python – handles all business logic. Python offers deep operating-system access, a massive ecosystem, and a gentle learning curve for contributors.
• Nuitka – an optimizing Python compiler that translates our code into standalone native executables. No interpreter required on the user's machine.

This combination lets us ship polished, self-contained applications that are as close to the metal as possible while remaining maintainable and welcoming to new developers.

Why not Rust, Go, etc...?

We love all those languages and use them where appropriate. However, Python + Nuitka gives us a unique advantage: rapid development without sacrificing the final user experience. Because Nuitka compiles to machine code, the user does not need Python installed and enjoys performance comparable to natively compiled programs.

That said, we are pragmatic. If a particular component demands it, we will use the right tool for the job.

How do you version your software?

We follow RomVer (Romantic Versioning), interpreted through our own strict scheme: project.major.minor.

project increments only when the entire application is rewritten from the ground up. This is a rare, monumental event.
major increments for any backward‑incompatible change — features removed, APIs renamed, or behavior that breaks existing usage.
minor increments for everything else: new functionality, optimizations, bug fixes, documentation updates. Do not be alarmed if minor numbers climb high; that is simply honest accounting of continuous improvement.

This scheme communicates the real nature of a release and aligns with our core promises of stability and transparency.

Privacy & Telemetry

Do you collect any telemetry?

We are completely against traditional telemetry that runs by default and harvests identifiable data. Our software never phones home without your explicit consent.

We are, however, open to the idea of anonymous, opt-in telemetry — where you voluntarily choose to share minimal, aggregated data solely for the purpose of making the programs you love even better. If such a system is ever introduced, it will be:

• Fully transparent (source code visible).
• Strictly opt-in (disabled by default).
• Documented in plain language about what is collected and why.

If you don't opt in, no data will ever leave your machine.

Does the software require an internet connection?

No. Every core feature works perfectly offline. We believe you should not need an account or a constant connection to use a calculator, a text editor, or a file manager. The cloud is an optional companion, never a prison.

Contributing & Support

How can I contribute?

Thank you for asking! There are many ways to help:

1. Code: Check our repositories for issues tagged good first issue or help wanted.
2. Documentation: Improve the docs, write tutorials, or suggest clearer explanations.
3. Translations: Help make our software and documentation speak your language. Every new locale opens the door for more people to participate.
4. Design & UX: Share your ideas for making our interfaces more intuitive.
5. Community: Answer questions on our discussion forums or help triage bug reports.
6. Donations: Support our developers financially so they can dedicate more time to the projects.

Visit our CONTRIBUTING.md for detailed guidelines.

How are donations used?

Every donation directly supports the people writing the code. Funds go toward:

• Compensating developers for dedicated development sprints.
• Covering infrastructure costs (domains, build servers, code signing certificates).
• Occasionally, acquiring test hardware to ensure native compatibility across platforms.

No one is getting rich here — we are all birds flying together. Transparency is a core value, so we publish financial summaries periodically.

Can I use Loosebird software in a commercial product?

Yes, depending on the license of the specific project. Most of our software is released under permissive licenses (MIT, Apache 2.0) or copyleft licenses (GPL). This means you can integrate it into commercial work as long as you respect the terms. Check the LICENSE file in each repository for exact details. If in doubt, open an issue and ask.

What operating systems and architectures do you support?

We aim for universal native support. Our primary targets are:

• Linux
• macOS
• Windows

On all these platforms we build for both x86-64 and arm64 architectures.

Because we use Nuitka and Slint, we can compile native executables for every target from the same codebase. Whether you are on a modern ARM single‑board computer, an Apple Silicon Mac, or a classic x86 workstation, the software meets you there — no translation layers, no compromises.

If you can help us test on a less common OS or architecture, we would love your help!

I found a bug or have a feature request. What should I do?

Open an issue on the relevant repository. Be as specific as possible: steps to reproduce, expected vs. actual behavior, and your system information. We take every report seriously because our users are our only stakeholders.

Didn't find your answer? Join our community forum or drop us a line. We're building this together.