Cross-platform field app
Ionic and Capacitor workflow for shipping one operational app across web and mobile while keeping native device behavior within reach.
I’m Benjamin—a full stack developer interested in the whole path: the screen, the service behind it, the data underneath, and the machine it runs on.
Now
2026 / 08Going back to C, seriously—to understand backend development from the socket up.
Frameworks make shipping possible. C makes the machinery visible. I’m revisiting memory, networking, processes, and I/O to build a more honest mental model of the backend.
Read the field note ↗Selected work
Ionic and Capacitor workflow for shipping one operational app across web and mobile while keeping native device behavior within reach.
Server-rendered and API-backed PHP applications with database-backed workflows, clear admin surfaces, and maintainable deployment paths.
Hands-on mobile work in Swift, Java, and Kotlin to understand platform conventions beyond hybrid wrappers.
C projects, Lua scripting, and current Rust study for deeper control over memory, performance, and runtime behavior.
The toolbox
Field notes
I’m returning to C to get closer to the fundamentals of backend development—memory, sockets, processes, files, and the work frameworks usually hide.
I dabbled with Electron for an internal project at work and learned a lot about connecting a React interface to a C backend, packaging desktop installers, and shipping across platforms.
Convex has made small app development feel much easier because I spend less time worrying about webhooks, caching, and keeping the frontend in sync with backend state.
I did not like Ionic at first because it felt like HTML wrapped in a mobile view. The things that changed my mind were the community, the tooling, and how easy it was to onboard new colleagues.
Have a project?
Let’s make something