Matt

@[email protected]
6 Followers
61 Following
42 Posts
Developer of Departing Earth
https://apps.apple.com/gb/app/departing-earth-spaceflight/id1641494756
Show threadMattOct 5
@samhenrigold don’t think this is a bug. I think this is because some sheets now appear with a zoom transition. I know for sure this happened with sheet content presented via the SwiftUI zoom transition on iOS 18 too! It is very inconsistent though.
Show threadMattApr 14, 2025

@caseyliss the latest Hacking with Swift - Unwrapped Live was focused on App Intents. Cannot recommend it enough, finally made it click for me. I believe it’s available via HWS+. Paid but very valuable.

Not super helpful but this was the most amazing resource I ever came across for the old way of doing it https://toolboxpro.app/blog/adding-shortcuts-to-an-app-1

Adding Shortcuts To An App: Part One — Toolbox Pro

When I decided I wanted to make a Shortcuts utility app , I downloaded Apple’s Shortcuts demo project ‘ Soup Chef ’ to try and figure it all out. It's a really excellent demo project, full of all the functionality that can be used to make complex shortcut actions, but since I was just starting ou

Toolbox Pro
MattMar 18, 2025
David SmithMar 17, 2025

Some really impressive work from my teammate Kevin here: https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585

If you care about Codable and/or serialization in Swift in general, definitely check it out

#swiftlang #swiftevolution

The future of serialization & deserialization APIs

Hello Swift Community, I’m happy to announce that I've been hard at work planning a potential future for serialization & deserialization APIs in Swift. It's clear from community adoption and feedback that Codable has had a lot of success in the years since it was added to Swift 4, but that it doesn’t satisfy some important needs. One of the foremost of those needs is performance more in line with programming environments that compete with Swift. As such, the main goal for this effort is to unlo...

Swift Forums
Show threadMattJan 17, 2025
@yanlu Pairs really nicely with .monospacedDigit() if you haven’t tried it already! Stops the width changing.
Show threadMattDec 19, 2024

@siracusa Honestly no idea. But wonder if it’s something like:

To me
.padding(.top, 2)
Reads as “add padding to top of 2”. You choose some edges and a value.

and
.padding(top: 2)
Reads as “Set all padding. Override the default value on the top edge to 2”. You set a value for each edge. You don’t really choose an edge. .topPadding(2) might be closer? Very different default value behaviour.

So might be really confusing to have both so similar. I can see some arguments for the first.

Show threadMattOct 17, 2024
@connected @imyke @viticci Was that Tea pun not intended or under appreciated? ‘Fortnum & Mason - Intellectual Proper-Tea specialists’
Show threadMattOct 2, 2024
@marcoarment Thanks for the heads up! 😬
They do seem to be breaking a lot of things recently (Although I am fairly new to CarPlay development). Nav bar buttons in the Info template just don’t work at the moment. Is it too optimistic to hope it’s the result of some massive updates being prepared behind the scenes? Have always felt SwiftUI would be perfect for CarPlay templates.
Show threadMattSep 21, 2024
@siracusa @marcoarment Also had some notification weirdness with this years transfer. Mail re-enabled notifications. I’ve had those badges off through a decade of transfers! Also lost my CarPlay app orders/settings and had to re-configure some Home controls in control centre.
MattSep 15, 2024
@stephenrobles @caseyliss This is referring to the Android app ‘Move to iOS’ right?
Some great sounding improvements for Android migration, that experience was never particularly smooth the few times I guided people through it.
Show threadMattJul 28, 2024

@9to5Mac

“Apple likely made this change so you could access Control Center from any app,”

If i remember correctly. Before the change you could do this by long pressing the bottom edge before beginning the swipe up. I assume they must have had some other thought process as well? Maybe it was just about discoverability, or maybe people found the app switcher confusing?