impizulu.com/blog

Why I built RayClay

by impizulu

At the start of the year I decided I wanted to develop my own app with the goal of releasing it on mobile, desktop, and web.

Probably like most developers, I wanted to build a closed-source app and distribute it to whomever I wanted. And I didn't want to have to pay any sort of fee or owe any conditions to the development tools I used. It turns out, this set of criteria really limited what framework I could choose.

Platform Support Breakdown

Framework Windows macOS Linux iOS Android Primary Strength
React Native Yes* Yes* No Yes Yes Mobile-first (JS/TS)
Qt Yes Yes Yes Yes Yes High-performance desktop & embedded (C++/QML)
Electron Yes Yes Yes No No Desktop apps using web tech (JS/HTML/CSS)
Flutter Yes Yes Yes Yes Yes Single UI codebase across all 5 + Web (Dart)
Tauri 2.0 Yes Yes Yes Yes Yes Lightweight web-UI apps with a Rust backend

*Maintained out-of-tree by Microsoft rather than the core React Native team.

I started by putting together a table that looked something like this. It was pretty clear to me that the best framework to use would either be Qt or Flutter. While Tauri has yeses for all platforms, I decided that it's dependence on platform-native webviews would probably mean excessive ongoing maintenance for me, the developer, which I would prefer not to have to deal with.

Random aside: I was surprised (and a bit disappointed) with how popular Electron is. Every Electron app ships a complete copy of Chromium (a full web browser with HTML/CSS parsers, layout engines, V8 JavaScript engine, and web APIs) plus Node.js. There are so many end-users sitting with all this bloat on their computer - what I would describe as software pollution. I think it's pretty unfortunate, especially since it's totally unnecessary - just pick a better framework (lol).

I was going to pick Qt over Flutter until I discovered its dual licensing model.

The Qt Licensing Issue

But using Qt comes with so many caveats that you are pretty much forced under their commercial licence. That means you have to pay. I did not want to pay.

E.g.

  • Add-ons like Qt Graphs, Qt Data Visualization, Qt Virtual Keyboard, Qt MQTT, Qt CoAP, and Qt Wayland Compositor. Using even one of these forces your entire app to be open-source unless you pay for a commercial license.
  • Even if I stuck to the LGPL modules, there was another catch if I wanted to distribute a single executable: I could statically link Qt and keep my source private, but I’d still have to make the files needed to relink the app with a modified Qt available to users. I didn’t want that obligation, and I didn’t want to pay for a commercial licence.
  • On top of that, it was annoying to have to figure out the licensing constraints in the first place.

So, with only a few very common criteria, I found that Flutter was the only framework that made sense. Which seemed a little ridiculous to me. And, admittedly, I did like Flutter. But after doing some perf measurements across Flutter and Qt, I realised how inefficient it was in certain key metrics like memory usage and on the CPU.

Ultimately, I realised that I was looking for a framework that didn't exist: lightweight like Qt but also convenient and fully open-source like Flutter.

Yes I did look at libraries like Dear ImGui but they did not have the out-of-the-box ease of development that I was looking for (flexbox-style layouts, networking, etc.). It was too DIY compared to the frameworks I looked at.

I wanted the performance of a lower-level framework with the convenience of less-performant frameworks. Is that really so much to ask for :/

Anyways, as a result I decided to build my own framework. Of course, I enlisted a swarm of AI agents (this project would have been futile to attempt solo just a few years ago) and I think RayClay has now reached the point where I can use it to build full-stack apps.

RayClay was born (1st commit) on 2026-05-21 and I plan to release v1.0 tomorrow 2026-11-21: exactly 6 months! Many, many after-work hours and weekends have gone into the project. But I think it's come together very nicely.