PaceVer (an alternative to SemVer, for mobile apps)
12 points
4 days ago
| 3 comments
| pacever.org
| HN
▲
encodedrose
15 hours ago
[-]
>MARKETING.NATIVE.OTA

Calendar Versioning (CalVer, YYYY.Release.Patch) fulfills the same need and you can see it in practice with Jetbrains (e.g. the latest version of IDEA is 2025.3.6).

The only difference is Jetbrains uses YYYY.R for marketing, see: "What's new In 2025.3"[1]

https://www.jetbrains.com/idea/whatsnew/2025-3/

reply
▲
aaronbrethorst
15 hours ago
[-]
I've been using calendar versioning quite happily with my mobile apps for a while now. It reduces the amount of angst and bike-shedding that comes along with otherwise rev'ing a major version number.
reply
▲
cdmckay
14 hours ago
[-]
In the article they call out that MARKETING can be date based
reply
▲
__m
16 hours ago
[-]
What’s the state of OTA updates, does Apple still prohibit them, or is it just not enforced?
reply
▲
tadfisher
15 hours ago
[-]
Officially, they are allowed if they consist of interpreted code and don't significantly change the functionality of the app as reviewed. Unofficially, they probably don't have a robust enforcement mechanism.
reply
▲
ea016
11 hours ago
[-]
For our mobile app we ended up doing YEAR.WEEK_NUMBER.BUILD. It makes it much easier for our team to know how old a version is (support, analytics, engineering). And regular users don't care about the version
reply