How we build

From concept
to shipped product.

We design, build and ship software on four platforms: the web, mobile, the desktop and Salesforce. Ideas are proven first in OpenSF Labs, our concept factory, and the ones that hold up become products, open source wherever they can be.

Four platforms

At home wherever your users are

Each product is built with the tools its platform does best: native code where it counts, and web apps that install and keep working offline.

Web

Installable web apps

Svelte · TypeScript · PWA

Apps that run in any modern browser and install to the home screen or desktop. Fast to reach, nothing to download from a store, and usable offline once loaded.

  • Offline-ready with a precached app shell
  • One adaptive layout for phone, tablet and desktop
  • Unit and browser tests in CI before every deploy
See Workbench Studio, built by us →
Mobile

Native mobile apps

Swift · SwiftUI

Apps that feel like they belong on your phone: fast, private by default and accessible from day one. Built for the newest hardware, including the foldable iPhone Duo, and taken all the way through App Review.

  • VoiceOver, Dynamic Type and reduced motion as part of the build
  • Privacy labels you won't need to apologise for
  • TestFlight builds along the way, App Store listing at the end
See Duor, built by us →
Desktop

Cross-platform desktop apps

Rust · egui

One codebase, native binaries for macOS, Windows and Linux. Rust gives us speed and memory safety without a browser engine in the box, so the apps start instantly and stay light.

  • A single native binary per platform, no runtime to install
  • Parallel by design: uses every core you have
  • CI that builds, tests and releases for all three platforms
See Alocir, built by us →
Salesforce

Apps native to Salesforce

Apex · LWC · AppExchange

Apps that live inside the org your team already uses, with no extra logins and no data leaving the platform. Backed by years of Salesforce architecture work, and published on AppExchange.

  • Packaged, security-reviewed and ready for AppExchange
  • Designed around the data model, not bolted on
  • Built for non-profits, NGOs, schools and small teams
See Alex, built by us →
The process

Four steps, from idea to release

Every product follows the same path, run in the open like the rest of our open-source work.

  1. 01

    Concept

    Ideas start in OpenSF Labs: small, working proofs that answer one question. Does it work, and is it worth building? We find out before anyone commits to a roadmap.

  2. 02

    Design & prototype

    Screens and flows that feel at home on their platform. A working prototype comes early, so decisions are made on a real device, not on a slide.

  3. 03

    Build

    Native code, in short iterations with test builds along the way, so progress shows as it happens, not just at the end.

  4. 04

    Ship & maintain

    App Store, AppExchange or GitHub Releases: we take the product through review and packaging, and stay around for updates after launch.

What goes into every app

The same care, on every platform

The right tool, not a wrapper

Swift on mobile, Rust on the desktop, Apex and Lightning on Salesforce, Svelte on the web. Each product is fast because it uses what its platform does best.

Private by default

We collect as little as possible, keep data where it belongs, and never add tracking you'd have to explain.

Open where it can be

Our own products are open source under a permissive licence. Read the code, fork it, and take the pattern with you.

Proven before it's built

Labs concepts answer the risky questions first, so the product build starts from something that already works.

Salesforce in the mix

Years of Salesforce architecture behind every app. For teams that live in Salesforce, the apps bring the right data and processes into one focused place.

Idea to release, end to end

Design, build, review, packaging and updates after launch. One small team, from the first sketch to the store listing.

See it in practice.

Every app here is free to use, and the source is on GitHub. Try one, read the code, or follow what's next in the Labs.