@MKBHD Myself and @NirajTiwari_ worked on getting our app EkAyu optimized for iPhone Duo with the Xcode beta version coz we wanted to be ready for this device.
https://t.co/YqoLF4f6ir
@SwiftDev_UI I tried that and sadly it does not, the only time when it works is when the duo is in its folded state thatโs when I can take the screenshots
Medical reports lost in your camera roll or paper bundle stacks?
I built EkAyu with my friend @NirajTiwari_ to keep your familyโs health records organised, private and easy to find.
Free on iPhone & iPad. Download ๐
https://t.co/YqoLF4f6ir
My buddy was irritated with one issue that he was having, and he and I had been working for a month to build something.
It was fun, it was learning, and it was having a good sense of accomplishment in solving a real problem in daily life.
More to come
You are a good developer till the time these agents donโt start hallucinating in a codebase you have either vibe-coded or have no clue what the AI coded till now.
Good day ๐ป
As AI usage increases in the IT sector, junior devs who once took 6โ7 years to become senior developers will now skip mid-level, senior, and tech lead becoming solution architects in 2 years and CTOs in 3
Temporary hacks quietly become permanent technical debt.
Even when a language or framework adds native support for a feature, codebases almost always keep the old workarounds anyway.
The feature ships, but the cleanup never happens.
@madskristensen Could the Exception Helper be resizable or respect the IDE font-size setting or have a setting of its own?
Its text is very difficult to read, have to increase the font size of the editor to get a decent read or copy paste the message in notepad to review the exception message.
AI can accelerate implementation. It cannot replace engineering judgment.
And no, a lengthy skill or spec file doesnโt solve that problem.
Lessons Iโve learned building software with AI
https://t.co/LPtjBc08qY
@simplydt Fair question. I havenโt measured a production delta yet, so Iโd avoid giving a % number.
The reason I called it out: Apple says AsyncImage now supports standard HTTP caching by default and respects server cache headers. That should reduce repeated image fetches when cacheable
WWDC26 brought some serious SwiftUI upgrades ๐
I broke down 5 changes iOS devs should know:
โข Toolbar APIs
โข Document API
โข Reordering
โข Swipe Actions
โข Performance + Data Flow
Bookmark this if you build with SwiftUI.
๐งต๐
Thatโs the full breakdown.
Follow @codecat15 for more SwiftUI, iOS, and Apple developer content.
Repost this for another iOS dev catching up on WWDC26 ๐
#SwiftUI#iOSDev#WWDC26
The Performance & Data Flow updates are worth paying attention to.
AsyncImage caching, lazy @-State initialization, ContentBuilder, and Xcode 27 build-time improvements can impact real production apps.
The way some accounts post these days is truly exhausting & immature.
- AI will make your job obsolete
- Did you know what just happened?
- Someone just crashed the real estate industry
Appreciate progress without turning every update into fear-mongering for engagement & like.