Lucas

Cross-platform apps

One shared core, built to feel at home everywhere

Keep the business rules in one place, then shape each interface for its platform.

Maintainability

Fix a rule once and every app stays in sync.

Platform knowledge

Each platform still needs people who know it well.

A good fit for your team?

For a small team, the extra FFI work may not pay off.

Test the real experience

Test the shared contracts, every adapter, and the real app on each platform.

Move at your own pace

Replace one interface at a time without rebuilding the whole product.

A familiar product, everywhere

A platform-specific interface can still feel unmistakably yours.

Three interfaces, one shared core

Python · Flet

class TodoCore(Protocol):
    def add(self, title: str) -> int: ...

todo_id = core.add(title)

TypeScript · React Native

interface TodoCore {
  add(title: string): TodoId;
}

const id = core.add(title);

Rust · Dioxus

trait TodoCore {
    fn add(&self, title: &str)
        -> Result<TodoId, Error>;
}

SOLID in practice

Small, focused ports keep platform code out of the core.

struct TodoStore {
    void *context;
    int (*save)(void *, const Todo *);
};

TodoResult todo_add(TodoStore store,
                    TodoDraft draft);

How the monorepo fits together

cross.clean/
├── core/
│   ├── domain/      # C++ business rules
│   └── c_api/       # stable C ABI
├── apps/
│   ├── flet/        # Python UI
│   ├── react-native/# TypeScript UI
│   └── dioxus/      # Rust UI
└── tests/
    └── contracts/   # adapter parity

How the pieces connect

Each interface reaches the same Todo core through a small adapter.
Mermaid
flowchart TD
    F[Flet / Python] --> A[FFI adapters]
    N[React Native / TypeScript] --> A
    D[Dioxus / Rust] --> A
    A --> C[Stable C ABI]
    C --> X[C++ Todo domain core]
See the working Todo example on GitHub

Kanban columns

Tic tac toe

A few words from people I’ve worked with

Jean-Pierre

Lucas has strong technical skills and showed them while integrating several of our systems. During the COVID-19 pandemic, we chose him because his training matched the expertise we needed.

Victorien

Lucas works independently and delivered what our small team needed. I trusted him because he takes ownership of his work and keeps learning.

Vivien

Lucas helped us with development, testing, and technical research. His versatility and broad knowledge made a real difference to the team.