Cross-platform sounds tempting. But then the small app turns into a heavyweight.

Digital products often have a core business logic. Extracting this centerpiece is a good idea, especially when the product needs to run on multiple platforms: mobile, desktop, and the web. Write the domain logic once, wrap multiple interfaces around it.

The web, in particular, presents specific challenges here:
1. Limitations in reusability as soon as the core contains more than just the logic.
2. The core should be as small as possible to reduce loading times.

The team at @zeitkapsl approached me with exactly these challenges. zeitkapsl is a service that offers end-to-end encrypted cloud storage for photo libraries.
They had already developed the core, but were hitting architectural limits. Furthermore, when integrating the core into the web browser, they reached the file size of an average MP3. They felt that was too large. So did I.

Such hurdles can be overcome with a strict yet simple architecture. I call it Domain Core.

A Domain Core ensures:
✔ Greater robustness and longevity of the cross-platform application (no more constant rewriting).
✔ Maximum flexibility for future platforms.
✔ A noticeably shorter time-to-market.

But before I dive into how we overcame these hurdles technically in the coming days, I’d like to know from you:
How would you approach such a problem? Or are you in a similar situation as the really nice guys at zeitkapsl?

Check out https://zeitkapsl.eu

#wasm #webassembly #domaincore #crossplatform #cleanarchitecture #softwarearchitecture

#CleanArchitecture is more complex, requires more boilerplate due to abstraction layers, and can feel over-engineered for small applications.
/Hot take