Quick reminder that the free limit reset from last month expires tomorrow at 9am PT! 🙏 If you haven't used yours yet, it's still waiting for you in Settings > Usage (or https://t.co/qXOsTIAjRH)
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! https://t.co/kFLEx5tlcg
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.
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.
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 https://t.co/yFTCHcgyA0
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.
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
🧵 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.
🧵 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.
I had a great time speaking with @KallamMostafa at @NSSpain about our migration to Bazel. We loved seeing how much interest it sparked and how many questions came in, so we wanted to share our answers here.
That explains the audience’s question on Linux. We’re exploring remote builds, including Linux machines. Running CI and giving agents their own build environments on cheaper machines is something we want to investigate.