I’m considering open-sourcing this project, if there’s further interest! I’ve never done this before, but I wonder how well an open-source “pay to download in the App Store” project performs.
Back when I was in the Air Force, I hated the UX for referencing Air Force publications on mobile. So I created an iOS app called AFI Explorer [0] which has continued to get hundreds of downloads every month for the past 5 years.
Since I’ve been shifting more towards platform engineering work in my career, the best reward abut this side hustle isn’t the financial benefit, but is the opportunity to stay grounded in software dev. I love seeing the changing APIs each year with the new iOS updates. And the seasonal approach to doing updates is always fun too.
I’m using this dependency project for my side-hustle iOS app development. When the number of authorized users matches the number of users with a valid installation, DeviceCheck simplifies the process.
[2] Vanity of vanities, says the Preacher,
vanity of vanities! All is vanity.
[3] What does man gain by all the toil
at which he toils under the sun?
[4] A generation goes, and a generation comes,
but the earth remains forever.
[5] The sun rises, and the sun goes down,
and hastens to the place where it rises.
[11] For I know full well the plans I have for you,
plans for your welfare and not for your misfortune,
plans that will offer you a future filled with hope.
[12] When you call out to me and come forth and pray to me,
I will listen to you.
These kind of complaints led me to try my hand at creating a new package manager for macOS[^1]. I really respect what the engineers at Chainguard have done with WolfiOS[^2] and tried to replicate the same - declarative package manifests which minimize the amount of dependencies. The project fizzled out after talking with some friends and realizing the futility when considering the global dominance of Homebrew.
reply