In the last post, we saw — and then ignored — a couple of interesting keywords: expect and actual. In this short post, I’ll give what I hope is enough of an explanation to satisfy the mildly curious.

In this installation in my Mobile App Development series, I’m going to introduce our next architectural layer, Decompose. We’ll look at what it is, why you might want it, and how to get started.

In this installation in my Mobile App Development series, we’ll take a look at the most foundational piece of the puzzle, Compose Multiplatform. We’ll see what it is and how to use it.

In recent years, I’ve found myself needing to build a mobile app here or there, and it has been, at times, a bit of a struggle as the landscape — and opinions about it — are wide and varied. There are debates about native, hybrid, and cross-platform approaches, and once you’ve made that decision, you have to wade through a lot of opinions on what library to use. This is especially true for the non-native approaches. What I’d like to do, then, is provide a how-to on the approach I have settled on, with a complete, working application to help someone else get started.

Years ago, I started this blog on Wordpress, then moved to awestruct, then to JBake, then to Jekyll. I’ve not done that because I like to change things (though I must admit I’ve enjoyed doing it each time ;), but because I’m looking for something that best suits my needs. I need to be able to post source code. It would be nice to be able to change theming — especially for source code — globally and easily. A static site would be nice for both performance and security. And as icing on the cake, being able to extend the build tool would be amazing. By chance in the past week or so, I was introduced to a new a tool, Roq, which is built in Java, and based on Quarkus. A whole lot of boxes were suddenly checked. Now, less than two weeks later, I’ve converted three sites, including this one. In this post, I’ll walk you through building your own static site that…​ Roqs. :P

Roq, of course, has its own documentation, which helped me immensely. However, as all docs go, there were some use cases that weren’t covered as thoroughly as I needed (or I’m slower than I like to think), so I thought I’d add my own voice, as they say, and maybe it will help you (and maybe help beef up the official docs. Andy, Roq’s author, has been super helpful and eager for feedback).