Los Altos, CA
- Tweets 707
- Following 140
- Followers 5,718
- Likes 239
Pinned Tweet
Prediction: every product with an iPhone simulator is going to start rendering it in a 3D device model.
3
1
24
6,443
This drawOn symbol effect is easy to take for granted, but it was actually a lot of work to get right.
1. SF symbols are not strokes. If you look closely at the signature, not all portions of the path are the same width.
2. Moving along the path and naively filling it would look awful! Consider filling along curves where one side of the path is shorter than the other. You want the animation to fill gracefully, but there's nothing that connects the two sides of the path.
The solution was to annotate each symbol with these "railroad track" guides
SwiftUI Tip 💡
Want an SF Symbol that draws itself on?
In iOS 26+, use .symbolEffect(.drawOn, isActive:).
7
16
431
39,578
Great use case for @bitrig Simulator Use
1
12
1,538
You don’t need to wait for a 3D duo sim. We shipped ours in @bitrig last week
iPhone Duo isn’t in your hands yet. But it can be in your simulator.
3D, photorealistic, interactive simulators: now available in Bitrig.
bitrig.com/blog/bitrig-build…
2
10
857
Bitrig + Sol 6 + Figma MCP one shot 🤯
Bitrig can now turn your Figma designs into native Swift apps built with Apple’s real controls and materials.
bitrig.link/blog/turn-figma-…
4
3
37
4,814
Lots of nice touches in this feature:
- Figma glass effect → Liquid Glass
- Plus lighter blend mode → vibrancy
- SF symbol code points → symbol names
- Design kit elements → native SwiftUI components
- ... and more
Bitrig can now turn your Figma designs into native Swift apps built with Apple’s real controls and materials.
bitrig.link/blog/turn-figma-…
3
5
50
5,359
Kyle Macomber retweeted
Before being acquired by Apple, I worked at @createwithplay for almost 5 years.
Designing, prototyping and building with real materials and Apple frameworks is really important to me.
I'm excited to share that today we're releasing Figma Import for Bitrig.
The easiest way to go from design to native Swift app.
Figma importers usually try to match your designs 1:1.
We wanted to go a step above, so alongside doing that, Bitrig can swap Figma's Glass effect for real Liquid Glass, use Vibrancy when an object has the Plus Lighter blend mode, and replace fake elements (screenshots of Maps, Tab Bars, TextFields, Navigation Views, Date Pickers, SF Symbols, Segmented Controls…) with the real thing, gaining the interactivity, responsiveness and accessibility the Apple frameworks and controls provide.
Bitrig will also connect pages and build the whole flow of your Figma frames and prototypes for you.
And one of my favourite features… this release works with the iPhone Duo, making it extremely easy to create apps for it while respecting all the Safe Area and reserved hinge regions, and to preview it in the 3D Simulator.
What else would you like to see our Figma Import do? Let me know!
Bitrig can now turn your Figma designs into native Swift apps built with Apple’s real controls and materials.
bitrig.link/blog/turn-figma-…
21
11
239
26,795
As you adapt your app for iPhone Duo, you may find yourself considering putting a NavigationSplitView inside a TabView.
It’s true that UIKit recommends against nesting a split view controller within another container in most cases[^1] and that many Apple apps treat the sidebar and tab bar as alternate presentations of the same navigation.
But there isn’t a blanket design rule against list-detail navigation within a tab. The distinction is what each view does:
- A TabView with the .sidebarAdaptable style lets people switch between top-level areas of your app, presented as tabs or a sidebar.
- A NavigationSplitView lets people navigate through a hierarchy, where selecting something in one column controls what appears in the next.
Those can be complementary. The pitfall to avoid is having multiple sidebars doing the same job.
In fact, the HIG even suggests using a sidebar within a tab on visionOS when your app’s hierarchy is deep[^2]. Just make sure the sidebar selection doesn’t change which tab is open!
If tabs organize your app’s sections and a split view gives each section a useful list-detail layout, I say go for it. A new form factor like the Duo is a good time to revisit old assumptions. But given UIKit’s historical guidance, be mindful you may encounter some rough edges.
This would be a good question for the UI frameworks team at a future iPhone Duo Apple Group Lab.
[^1]: developer.apple.com/document…
[^2]: developer.apple.com/design/h……
The @pushpushapp Duo adoption is coming along nicely in @bitrig. NavigationSplitView has been my best friend.
Video on my journey coming soon.
3
9
140
34,002
Kyle Macomber retweeted
Didn't expect to get this far but porting/remaking Diablo II for iPhone Duo on @bitrig has been a breeze. Even got sound and music working.
4
7
35
7,758
Kyle Macomber retweeted
I used Astra to make a Codex Micro emulator for iPhone Duo using Metal (sound on!)
23
15
429
95,257
This will be our 25th major release of @bitrig in 25 weeks 🚀
6
3
30
4,439
