Apple announced during its WWDC keynote that iOS apps will run on macOS, starting with the next major release of macOS this fall — macOS Catalina. Third-party developers will be able to release. It’s the first app that you see the moment your Mac completes the startup process. It opens right away and stays active as you use other apps. To use this app to sync Catalina with an iPhone or vice versa, follow these instructions: Make sure your iPhone is connected to your Mac using a Lightning cable.

Backup Iphone On Mac Catalina
Best Mac Catalina Apps
Run Iphone Apps On Mac

Streaming is available in most browsers,
and in the WWDC app.

Apple silicon Macs can run many iPad and iPhone apps as-is, and these apps will be made available to users on the Mac through the Mac App Store. Discover how iPad and iPhone apps run on Apple silicon Macs, and the factors that make your apps come across better. Learn how to test your app for the Mac, and hear about your options for distribution of your apps.
Resources
Related Videos
WWDC 2020
WWDC 2019
Download
Hello and welcome to WWDC.
Welcome to 'iPad and iPhone Apps on Apple Silicon Macs.' My name is Jason Beaver, and I'll be joined later by my colleagues James Snee and Patrick Heynen.
As you may have seen in the Keynote or State of the Union talks, Big Sur on Apple Silicon allows you to run iOS apps natively on the Mac without recompilation.
The Mac is a robust platform for development that enables all kinds of apps. There's everything from powerful desktop apps to web-based experiences and graphic-intensive games. These experiences are all powered by our dedicated UI frameworks.
In macOS Catalina, we added the ability to build your iOS apps for the Mac with Mac Catalyst. Mac Catalyst makes UIKit a native peer to these other UI frameworks on the Mac and enables you to bring your iOS apps over to the Mac as first-class experiences.
You can refer to last year's 'Introducing iPad Apps for Mac' session to hear all about how we did this.
Mac Catalyst requires building your app with the macOS SDK and gives you the ability to customize and optimize your application to take full advantage of the Mac.
In macOS Big Sur, we are leveraging this Mac Catalyst infrastructure to enable running your existing iOS apps as-is on Apple Silicon-based Macs.
Here, 'as-is' really means 'as-is.' We enable the user on the Mac to purchase or download, through the Mac App Store, the application you've already made available on the iOS App Store. It is the exact same binary.
Because these apps use the same underlying infrastructure that is used for Mac Catalyst apps, the same unified frameworks and the same iOS frameworks brought over and integrated with the Mac, your iPad and iPhone apps get a tremendous amount of behavior automatically, making them feel right at home on the Mac.
However, they don't have access to all that a Mac app would like to offer. If you want to take your iOS applications further on the Mac, create a Mac Catalyst version by checking that switch in Xcode. This will give you the ability to customize your app's behavior on the Mac, as well as allow you to distribute your application on all Macs, not just those running Apple Silicon.
For your app to be available in the Mac App Store, it must be compatible with the Mac.
Your app can't be dependent on an unavailable symbol or framework, it can't be dependent on missing functionality in existing frameworks, and it can't be dependent on hardware capabilities that don't exist on the Mac.
Compatible iOS apps are automatically available in the Mac App Store, but you can manage the availability of your app in App Store Connect. You might choose not to make your iOS app available in the Mac App Store if you already have a Mac app or are planning on shipping one or if your app doesn't make sense on the Mac.
Patrick will discuss this further later in the session.
Most existing iPad and iPhone apps run great on macOS, but the environment has some differences that you should be aware of.
These fall into three categories: hardware differences, UI differences and system software differences. Let's start with hardware differences.
iOS is built around a direct, multi-touch interaction model, but macOS is built around an indirect, cursor-based interaction model.
The infrastructure automatically maps many multi-touch gestures, but if your application uses custom touch handling, you should test whether your application is compatible with the Mac. If your application supports keyboard entry as an alternative to your custom touch handling, that will also help your app be more compatible with the Mac, as well as a better experience on iOS.
iOS devices have a range of sensors that aren't available on Macs, such as accelerometers, gyroscopes, magnetometers, depth-sensing cameras and GPS.
By dynamically confirming in your code that the appropriate sensor is present, you can ensure that your app is compatible with the entire range of iOS devices, as well as compatible with the Mac.
Note that not all APIs that are dependent on these sensors fail to work on the Mac.
For example, even though Macs do not contain GPS receivers, they do support Core Location and can provide position information to your app, though it will be less precise than it would be with GPS.
iOS devices typically just have front- and rear-facing cameras. Macs, on the other hand, may have built-in front-facing cameras, like in our laptops and some desktops, but may also include cameras built into external displays or cameras plugged in via USB.
iOS apps may not be prepared to deal with all of these configurations, but using the AVCaptureDeviceDiscoverySession instead of enumerating all of the AV capture devices will allow us to ensure that your app has access to the most appropriate camera for your needs.
Now, let's talk about some UI differences.
As we discussed before, iOS apps automatically get a great deal of system behavior from macOS.
This will necessarily look and behave differently than on iOS devices. For example, alerts and pop-ups may show up in different locations on the Mac and Open and Save panels will show in separate windows.
This means that it's important that your app does not hard-code any assumptions about the UI, like the location of system UI, since those assumptions might be wrong when running on the Mac.
On macOS, windows are typically resizable by the user. If your iPad app already supports multitasking on iOS, it will be fully resizable on macOS.
This means that it can run at a wide range of sizes, not just the small number of fixed sizes supported by iOS multitasking.
Using Auto Layout will help you ensure that your app can run correctly at any size.
Window resize is also live on macOS. Optimizing the performance of your application layout will improve the resize experience on the Mac and make your app even more responsive when multitasking on iOS.
If your iPad app does not support multitasking, or if you have an iPhone app

Resources

Related Videos

WWDC 2020

WWDC 2019

Run Iphone Apps On Mac Catalina