[ChrisMarshallNY]

I tend to ship fairly quickly, at a high Quality (but not perfect) level, then go back and clean up, after it’s out there.

It’s important that the first release be extremely high Quality. I’m not a fan of lash-up MVPs.

I work very quickly, and do good work.

I just did that with the 2.0 version of one of my apps. I released 2.0 a couple weeks ago, and it’s at 2.1.4 (I think). I test, and solicit feedback. One of the releases covered feedback on the App Store.

It stops, after a few tweaks.

[ChrisMarshallNY]

Interesting. Whenever I talk about Quality, the downvotes appear. It's almost as if people are actively against the concept of high-Quality software.

This is not some idle boasting. This is a project with a great deal of history.

Here's the app, itself, in the App Store: https://apps.apple.com/us/app/ambiamara/id1448933389

It started off as "SpeakerBeeper," in ObjC, ten years ago. Here's the codebase for that: https://github.com/LittleGreenViper/speakerbeeper

It then became "X-Timer," in 2015-17, after Swift came out. Here's the codebase for that: https://github.com/LittleGreenViper/x-timer

This is the current codebase for the "AmbiaMara" app, which has been out for the last three years or so: https://github.com/RiftValleySoftware/ambiamara

The codebases show a lot of learning and growth. You can easily see how fast I work, and how I'm able to maintain a fairly high level of Quality, throughout the project.

Yeah, it's just a silly timer, but it's a good one. I use it constantly. I basically wrote it for myself. A lot of my work is like that.