martiancraft.com

If you’ve got an existing Mac Catalyst app that’s not been built for Big Sur, then first you’ll want to get the app running on macOS Big Sur, which may require some tweaks to the design to ensure that the app fits with the new UI concepts in Big Sur. Mac Catalyst apps actually receive a lot more first-class treatment in macOS Big Sur that allows these apps to further look and behave like native macOS apps. If you have an iOS SwiftUI app, this app can be transitioned (and new views be built where Mac-specific variants are warranted) to a universal app and built for Apple Silicon. If you have an iPadOS version of your iOS app, then you can create a Mac Catalyst version of the iPadOS version of the app that will run like a native macOS app.

In the above section, you found out how to manually fetch an LPLinkMetadata object that you can use to build out a custom UI in your app with additional metadata about a URL, but the real power with LPLinkMetadata relies on LPLinkView can be instantiated in your Storyboard scene, or manually in code. There’s no object in the object picker in Interface Builder, so you’ll need to manually drag out a UIView object to place in your scene, then set the class to be LPLinkView, then set an IBOutlet in your code to reference the object and set the metadata once fetched, like so: Once you’ve done this, the link view will be populated using the image preview if available, or video player if the link is a video link. You can still use this link view to deep link throughout your app (or to another app) by creating your own metadata object and passing it into the link view.

As more and more information comes to light in the wake of Parler’s implosion it is becoming clear that the entire platform was built upon a house of cards of cutting technical corners, and gross mismanagement of user’s private and personal data. When building a platform where user data will be collected, both directly and indirectly, it is of utmost importance to be clear with how user data will be used and respect the user’s request to actually delete it. Any social app that is built for users to post their own content should have some sort of mechanism to turn off comments by a user, or disable that user entirely in the event that they are abusing the system, abusing other users, or causing other harm. Parler’s CEO has recently stated that when and if Parler returns it will implement keyword based algorithmic moderation [source] Regardless of which content moderation scheme you pick, at the end of the day, the user’s account isn’t truly their account.

It hasn’t gone unnoticed to me that probably the most important announcement today was one similar to that announced at my very first WWDC in 2005 with the rollout of the transition from Motorola to Intel processors in the Mac. Apple offered a number of “updated” transition technologies that should make life much better for developers and users — from the “Universal 2” that will allow developers to “easily” rebuild software for both platforms to “Rosetta 2” that should allow users to run legacy Intel software until updates are provided (hopefully). Clearly, Apple will no longer be constrained by Intel and Intel’s general computing platform use cases and legacy users. Until we see the first production hardware, it’s hard to know what this will mean for the production software that many Mac users live with daily.