Open source is a starting point, not a guarantee
Open source applications make their code available for inspection, learning and adaptation. That makes independent review possible, but does not automatically make software secure or private. Architecture, dependencies, testing and release practices matter too.
ConnectApp shares applications as starting points, with documentation and honest information about development maturity. Our aim is not to promise perfect privacy; it is to help people make informed choices.
What local-first storage means
Local-first software prioritises processing and storing data on the user’s device. There are meaningful potential advantages:
- Fewer unnecessary data transfers: not everything has to pass through a remote server.
- Greater autonomy: some tasks can keep working without internet access.
- More user control: information can remain on the device, often with export or backup options.
- Less infrastructure: a small application does not always require cloud hosting or a remote account.
Yet local-first introduces responsibilities, too: backups, encryption, updates, device loss recovery and protection against shared-device access still need attention. Not every feature can or should run fully offline.
Three ConnectApp examples
BudgetApp: storage is a choice
BudgetApp is a Python and PySide6 desktop quotation manager. Its README supports both local SQLite and remote MySQL. It would be misleading to call it exclusively offline: privacy also depends on how it is configured.
PhysioApp: sensitive information requires validation
PhysioApp manages patient and professional records on tablets. It includes local persistence, authentication safeguards and encrypted backups, but remains pre-alpha. Real clinical use requires project-specific technical, functional and legal validation.
MiBotiquinApp: privacy with optional integrations
MiBotiquinApp organises medication reminders, doses and inventory. Data is stored locally, but optional CIMA/AEMPS catalogue lookups and scanning features may use external services. Transparency means disclosing these exceptions instead of concealing them.
Reusing code responsibly
The Apache 2.0 licence permits studying, modifying and distributing projects, including commercially, under its conditions. Reuse still requires checking third-party licences, security, tests, data processing and legal requirements for the resulting product.
Each ConnectApp page introduces the application, its technology and a link to the repository. For implementation decisions, always consult the actual source code and project README.
How we want to build
We want the ConnectApp website to embody similar principles: accessible content, static pages without advertising trackers, and optional transparent financial support. Not every recommendation has to become an affiliate link.
Open software deserves precise explanations, not absolute slogans. That is what we want ConnectApp to stand for.