David retweeted
I’ve gotten my Claude Code setup to the point where I am no longer doing data entry around credentials and it is glorious! Rarely do I need to go to my computer now, so I asked my orchestrator session to write up the setup in a post for your agents! daniellemorrill.com/blog/how…
David retweeted
Now in @matte_app your agents can write Code clips, so your mockups and screen recordings can have complex animations and shaders in the canvas with them.
Graphs, backgrounds, shapes, particles… anything you want.
Code clips automatically get custom controls so you can tweak them yourself and stay in control.
David retweeted
The Matte MCP is such a great way to get great videos with barely any effort. Matte auto-animates the iPhone Duo recordings and your AI agent takes care of the rest.
David retweeted
Matte is the best way to make your iPhone Duo videos. Record the simulator and ask Claude to do the rest via MCP!
Undolly is almost ready for iPhone Duo. Here's a sneak peak made with @matte_app
mav is ready for iPhone duo. If you are building for iPhone duo using agents give it a try. mav can now manage the hinge, tap inner pannel, take screenshots and videos and works with device hub. Free, open source, skill ready github.com/bitomule/mav
David retweeted
A reminder for indie devs:
If your app makes $5/month, you’re already ahead of most apps on the App Store.
You shipped.
A stranger found your app.
They liked it enough to pay you actual money.
That’s fucking hard.
ASO, growth, marketing… you can figure that out.
But you already did the hardest part:
You built something people are willing to pay for.
Don’t forget that.
David retweeted
Oh come on. Quick look at colorshift (13x faster): HashMap in hot loop (unoptimized Rust vibeslop) is slower than indexed arrays (ASM). No shit. Numbers like 17x should raise eyebrows but reading the comments nobody is thinking anymore. This AI psychosis has fried people's brains
I ported the Omarchy screensaver engine (ttfx) from Rust to x86-64 assembler, and it's up to 17x faster!! One-shot translation by Opus 5.5. We keep drilling until the agentic drill bit hits bedrock! github.com/omacom/ttfx/pull/…
David retweeted
Final takeaway: iOS devs should almost always start new projects in bazel, agents; and huminity will love you. It's way easier than anytime before.
What did we miss from Tuist that we found in Bazel? Detailed thread by my dear @KallamMostafa
David retweeted
🧵 Re: Which features Tuist did not have that you needed ?,
The answer will be quiet long and detailed one. (Also: photos of Logroño as well 🍇)
The summary is: there were technical limitations for tuist, and non technical ones, both contributed to our final decision.
Replying to @Bitomule
We evaluated Tuist and would choose Bazel again for our project. Its capabilities and long-term foundations convinced us. We're still moving more work into Bazel, and local machine capacity is becoming our next constraint.













