| Nil Coalescing blog | https://nilcoalescing.com/blog/ |
| Exsto drawing app | https://exsto.app |
Creating a seamless user experience in Swift involves managing and clearly communicating errors. User-friendly descriptions and recovery suggestions for custom errors help guide users in resolving issues, making applications more intuitive: https://nilcoalescing.com/blog/UserFriendlyDescriptionsAndRecoverySuggestionsForCustomErrorsInSwift/
If you are using Swift Charts in your projects, check out my blog posts to explore some advanced techniques 📈:
Area chart with a dimming layer: https://nilcoalescing.com/blog/AreaChartWithADimmingLayer/
Using Foundation Measurements for values in Swift Charts: https://nilcoalescing.com/blog/UsingMeasurementsFromFoundationAsValuesInSwiftCharts/
Fill bar marks with gradient: https://nilcoalescing.com/blog/FillBarMarksWithGradient/
@moirearty Yes very much so, when you consider the remote mirroring works even when the phone is locked.
Having a method that lets any other device within BT/Wifi range unlock and remotely drive a phone without the HW security of the paired cyrpgrphic handshake between the secure enclaves of both devices is going to require a LOT more work.
@malauch One of the differences with automative regulation is the clarity on what is and is not permitted.
The DMA is intentionally very vague in a way that you don't see with seatbelt or crumple zone regulation.
It would take a LOT more work to make iPhone mirroring and remote controle be exposed to third parties in such a way that it matinees the same level of security and is an API that apples teams want to commit to long term. Not to mention the system ML access for DMA.
@malauch Yes but that is extra work, for any feature that might possibly fall under the DMA they are required to go put in extra work to ensure that they provide this parties access to it. (thus committing them to an API they then must support)
The DMA does not have the ability within it for apple to seek pre-aproaval they cant check with the commission in advance, all they can do is delay features or risk a legal battle.
DMA is not just about apps it also covers system features and services. There is clearly un-certainty within the teams with respect to the iPhone Mirroring feature and if that would be required to be exposed otherwise they would be shipping it.
As for remote controle, yes they should have an api to let other screens sharing apps (that already exists). But that will require more work.
@mysk I expect it is both, so long as apple have data centres within the EU the GDPR issues are not that much of an issue. GDPR is known and mostly undestood.
DMA is not, the questions are raise with the DMA would apple be required to let third party models run on apple private cloud (would it be an unfair competition if thee are apple only?).
Should other third party ML models on device have raw access to the same user data as Siri?....
@stroughtonsmith yes and no,
There are areas were the DMA is unclear on how much access the platform vendor must provide day one to third parties.
Eg does the DMA require apple expose apis so that MS and Linux devs can implement iPhone mirroring?
Is this an iPhone platform feature or a Mac feature, so does it fall under the DMA or not?
These are legit questions that are unclear and would likely require a good bit of dev work to comply with securely.
The Swift language constructs `self`, `Self`, and `Self.self` can be confusing, even for experienced developers.
🔹 `self` refers to the instance of the type within its own instance methods.
🔹 `Self` refers to the type that conforms to a protocol, allowing for polymorphic behavior.
🔹 `Self.self` is used to refer to the metatype of the type, essentially the type of the type itself.
You can read more on these constructs in my blog post: https://nilcoalescing.com/blog/UseCasesForSelfInSwift/
Natalia Panferova
