wip: Adding overview page

Author: ivanpovazan

docs/core/deploying/native-aot/ios-like-platforms/creating-and-consuming-custom-frameworks.md

@@ -1,6 +1,6 @@
 ---
-title: Building native libraries for iOS-like platforms
-description: How to build and consume native libraries with Native AOT for iOS-like platforms
+title: Create and consume custom frameworks for iOS-like platforms
+description: How to create and consume custom frameworks with Native AOT for iOS-like platforms
 author: ivanpovazan
 ms.author: ivanpovazan
 ms.date: 11/21/2024
@@ -50,10 +50,6 @@ This section describes steps to create a simple .NET Class Library project with
 
 5. Publish the class library and target the desired iOS-like platform by specifying the appropriate runtime identifier (referenced below as `<rid>`):
 
-    - For iOS physical devices use: `ios-arm64`
-    - For iOS simulator devices use: `iossimulator-arm64` or `iossimulator-x64`
-    - For MacCatalyst use: `maccatalyst-arm64` or `maccatalyst-x64`
-
     ```bash
     dotnet publish -r <rid> MyNativeAOTLibrary/MyNativeAOTLibrary.csproj
     ```
@@ -65,7 +61,7 @@ Successful completion of the previous step produces a pair of files: a shared li
 > This means that you need to repeat step 5 with a different runtime identifier.
 > For example, you'd publish the class library with both `maccatalyst-arm64` and `maccatalyst-x64` runtime identifiers as a prerequisite for [Packaging the shared library into a custom MacCatalyst universal framework](#package-the-shared-library-into-a-custom-maccatalyst-universal-framework).
 
-## Create and consume a custom framework (optional)
+## Create and consume a custom framework
 
 Apple imposes a requirement that shared libraries (.dylibs) need to be packaged into frameworks in order to be consumed from applications.
 

docs/core/deploying/native-aot/ios-like-platforms/index.md

@@ -8,6 +8,37 @@ ms.date: 11/21/2024
 
 # Native AOT support for iOS-like platforms
 
-TBD
+Starting from .NET 8, Native AOT supports targeting iOS-like platforms. The term **iOS-like platforms** refers to Apple platforms that use similar APIs such as: iOS, MacCatalyst and tvOS.
 
-For specifics of building and consuming native libraries, see [How to build and consume native libraries with Native AOT for iOS-like platforms](./creating-and-consuming-custom-frameworks.md).
+In the first release, the support was experimental, while in .NET 9 these platforms received full support with Native AOT.
+
+Based on the use case, the support can be divided into:
+
+- support for assemblies referencing OS-specific APIs through .NET mobile workloads (like: .NET MAUI apps)
+- support for assemblies without OS-specific API dependencies
+
+The former is a more common scenario and is described in detail in [How MAUI supports Native AOT](/dotnet/maui/deployment/nativeaot).
+For the latter use case Native AOT deployment can be achieved by:
+
+1. Enable Native AOT deployment by including the following properties in the project file:
+
+    ```xml
+    <PublishAot>true</PublishAot>
+    <PublishAotUsingRuntimePack>true</PublishAotUsingRuntimePack>
+    ```
+
+2. Publish the project for the desired iOS-like target platform by specifying adequate runtime identifier (later referred to as `<rid>`):
+
+- `ios-arm64`, for iOS physical devices
+- `iossimulator-arm64` or `iossimulator-x64`, for iOS simulators
+- `maccatalyst-arm64` or `maccatalyst-x64`, for Mac Catalyst
+- `tvos-arm64`, for tvOS physical devices
+- `tvossimulator-arm64` or `tvossimulator-x64`, for tvOS simulators
+
+and execute the following command:
+
+```
+dotnet publish -r <rid>
+```
+
+For specifics of building and consuming native libraries on iOS-like platforms, see [How to create and consume custom frameworks with Native AOT for iOS-like platforms](./creating-and-consuming-custom-frameworks.md).