Events π
β Actions users perform inside the app π±οΈ
β Reveals which features are actually used π οΈ
β Drives real product decisions π‘
Sessions π
β Number of times the app was opened π
β Shows how often users come back π
β Reflects overall engagement trends π₯
So whatβs left? π€
Build my own analytics service?
β Lightweight events β‘οΈ
β Lightweight data storage ποΈ
β A simple, focused dashboard π
β Meaningful data, not vanity metrics π―
Just:
Events β Insight β Decisions.
So I did it for our @sip_app
Sentry @sentry is excellent π
But itβs not product analytics.
Itβs:
β Crash reporting π₯
β Performance monitoring β‘οΈ
β Release health π₯
It tells you when things break.
Not how users behave.
Reliability, yes β
Product insight, no β
TelemetryDeck @Telemetry_Deck is very Apple focused π
β Love the positioning.
β Love the privacy angle.
But the dashboard feels hard to analyse π§
When analysing data creates friction,
you stop using it.
And unused analytics is useless analytics π«π
Aptabase @aptabase is clean and privacy friendly π
Great philosophy.
Great for lightweight tracking πͺΆ
But for deeper product decisions, it feels too minimal.
If you want:
β Cohorts π₯
β Advanced retention β»οΈ
You hit limits.
Excellent for simple metrics π
Not enough for strategic analysis.
Microsoft App Center @vsappcenter was actually solid π§©
β Event tracking π
β Basic funnels π
β Crash reporting π₯
β A clean dashboard π₯οΈ
Not perfect.
But it struck a good balance βοΈ
It was retired on March 31, 2025 πͺ¦
Since then, the gap is obvious.
Analytics for macOS apps is still painful π©π»
Sending events is easy β‘οΈ
Making decisions from them is the hard part π§ π
Most tools either:
β Donβt go deep enough π€
β Or make analysis harder than it should be π
Analytics should bring clarity β¨
Not dashboard confusion π€―
Honestly, it feels controlled, predictable, and kind of addictive in a good way.
β Ask for small changes only
β Review the suggestion and accept it if it looks right
β Build the project in Xcode to make sure everything works
β Open the GitHub client and carefully check the diff
β If everything looks goodβ¦ next prompt π
And thenβ¦ TADAAAAAAAAAA β¨β¨β¨
Iβm kinda new to Codex CLI and honestlyβ¦ I think I found a really nice flow ππ₯
I tried making a few adjustments on
github.com/ruiaurelian...
Not sure if this is the βbestβ way, but it feels super safe and smooth for me.
This is basically how I do it:
Much better experience. Iβm actually happy with the issues it detected and the improvements it suggested.
Today I used Codex CLI for the first time.
I ran it locally against my PHP API to detect issues and possible improvements.
The first run completely broke everything π€£π€£π€£
So I changed the approach and asked it to work step by step, showing each change so I could accept or reject it.
Happy new year ππ
That makes me wonder, did AI actually get worse, or did we just get used to it and become more demanding? Are our expectations higher now?
Lately, though, it feels confusing as hell. Many answers are vague, wrong, or overconfident, and I spend more time double checking than actually moving forward.
When I first started using AI to help with code, it felt genuinely useful. Answers were clearer, suggestions made sense, and it often saved time.
Merry Christmas π
π SF Symbols Lite 1.0.1 is out.
β¨ You can now check for new builds and download updates directly from the app.
β±οΈ Search feels calmer with an improved delay, plus refined bottom tag colours.
β¨ Built specifically for macOS 26. Feedback is always welcome β€οΈ
So I built something very small and very boring, in the best way.
SF Symbols Lite checks this endpoint:
api.github.com/repos/ruiaur...
It parses the JSON, compares versions, and tells you if there is a new update. Thatβs it.
I wanted a simple way to manage SF Symbols updates.
Sparkle is great, but for this use case it felt like overkill. I did not need delta updates, signatures, or a full update framework. I just wanted to know when a new version was available.
πβ¨ Thanks for all the shares and likes
π¬π‘ Really appreciate all the suggestions and feedback
βοΈπ If you like the project, give the repo a star
π Iβve been working on this project just for fun, and Iβm happy to share that itβs now open source.
β¨ SF Symbols Lite is a lightweight, fast alternative to Appleβs SF Symbols app, focused on better search, custom tags, and a clean macOS experience.
β¨ macOS 26. β€οΈ
β github.com/ruiaureliano...
This happens a lot when you try to write a swift float into a JSON or a XML file, in seen many times
This works fine, but if I move the extension to another file like βPerson+Update.swiftβ, it stops working.
Is there a way to allow this, similar to protected in Java, so members stay accessible to the class and its extensions in other files?
Still looking for my next iOS/macOS role. Swift, remote, and ready. β‘οΈ
This is beyond annoying. Apparently, Apple Mail skipped basic math class, because it clearly canβt count. Happens all the time, such a reliable app, truly.
SF Symbols Lite
SF Symbols is great, but I always felt something was missing.
So I started this as a little side project.
Of course, you can (and should) keep using Appleβs SF Symbols, itβs fantastic.
But there are some symbols I never touch, and others I wish existedβ¦ so Iβm making my own π
β¨ Something small, simple, and kind of magical is coming.
Think of it as a lite version of SF Symbols, but with a twist.
What features would you love to see in a minimalist, focused SF Symbols companion?
Maybeβ¦ faster search? Tags? Symbol previews? Something secret? π
I canβt say too much yet.
