Native software for Mac, iOS, Windows and Android — and the tools underneath.

We have made no secret about our frustrations with getting things through the Google Play Store. The distraction that working through their process has represented is arguably even more frustrating. We have a long list of additional projects that we want to tackle, but the time spent on Google and their policies is, in a word, obscene. When we last posted on Oct 17th, we figured we were pretty much 'done' and had no chance of ever meeting their demands. An appeal was filed, and we thought to move on to other projects.

At this point, I think we can safely say that the Bike Law Pocket Guide is unlikely to ever make it into the Google Play Store. So, with that said, we are enabling side loading the APK to any Android device, and moving forward with the project on all of the platforms, just acknowledging that Google Policy implementation and decisions create a difficult situation for the Pocket Guide. What follows is long, detailed, and we suspect quite clear on the frustrations that we feel regarding Google, the Play Store, and their process.

If you do not want to get into that, now would be a good time to wander off and go for a bike ride. However, if you want the full nitty gritty details, read on.

Full disclosure, some of what follows is as much a product of being new to the quirks of each of the various app stores, as well as general frustration for a developer that has spend 3 decades in this business either selling direct, or licensing to other people to deal with the retail side of the business. When we have elected to make things available in the past, we have often used the donation-ware model, simply because it was convenient and easy.

If you use Claude Code, Cursor, or Windsurf on a real project, you've probably already reinvented ISSUES.md. Nobody standardized it, but it spread anyway, because it solves a real problem: give the agent a work list it can read without a network call, and a place to write back what it fixed. No server, no account, no context switch out of the editor. It lives and dies with the commit history like everything else in the repo.

It also breaks down. Not immediately — at five issues, a hand-written markdown list is completely fine. The trouble starts around fifty.

This evening we have made available the KDE implementation of the I Have Issues application. Download, unzip, follow the directions in the README to build and install. Bear in mind, this is not a primary use platform for us, so the application does not get quite as much use as the other platforms.

This morning we have made available the Gnome implementation of the I Have Issues application. Download, unzip, follow the directions in the README to build and install. Bear in mind, this is not a primary use platform for us, so the application does not get quite as much use as the other platforms.

Download for Gnome

With todays approval by Apple, I Have Issues is now fully in the wild. Mac OS app available via direct download and the Apple App Store, Windows 11 builds for both x64 and arm64 available via direct download. Donations accepted.

... Add up to make a big thing, and this last weekend has been a very long list of little things, along with a couple of big things. Let us start with the little things.

So, this might not be worth its own news entry, but the new look and feel website dropped today. It wasn't supposed to happen until tonight, but apparently someone forgot to disable the auto publish features that we have been using during all of our recent tweaking, and well... oops?

Anyways, much like the work we did over at Two Wheel Junction, it was time. Most of the existing site dates back to 1995, and despite multiple minor updates, it had reached 'well over due' status. While a more flashy look would be the trend, it just did not fit quite who we are, so we opted for a lower key, more 'hey there is stuff to actually read' layout and look.

We hope you like it.

FiSQL is an idea. Pronounced like 'fiscal', the idea is an accounting system that works for your business. Implement the modules you need. Ignore the modules you don't. Own your data. Customize the system to your needs. Integrate it with the tools you want, or create your own.

FiSQL is the operating system for a small business: customers, vendors, bills, invoices, the general ledger, projects, time, and support tickets - with stock and warehousing still to come. It runs on a real SQL database you can point any tool at, and it grows one module at a time rather than arriving as a suite you have to swallow whole. The one-sentence version: run your whole business on a database you own.