You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/includes/best-practices-native.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Here are the minimum OS platform requirements to ensure optimal functionality of
41
41
42
42
## App request device permissions
43
43
44
-
To use the Calling Native SDKs for making or receiving calls, it's necessary to authorize each platform to access device resources. As a developer, you should prompt the user for access and ensure that it's enabled. The consumer authorizes these access rights, so verify that they have been granted permission previously.
44
+
To use the Calling Native SDKs for making or receiving calls, it's necessary to authorize each platform to access device resources. As a developer, you should prompt the user for access and ensure that are enabled. The consumer authorizes these access rights, so verify that they have been granted permission previously.
45
45
46
46
### [iOS](#tab/ios)
47
47
@@ -106,11 +106,11 @@ It's important to note that on mobile devices if multiple processes try to acces
106
106
107
107
## Optimize the APP size using UI Library
108
108
109
-
Optimizing the size of libraries in software development is crucial for several reasons, particularly as applications become increasingly complex and resource-intensive.
109
+
Optimizing the size of libraries in software development is crucial for several reasons, particularly as applications become increasingly complex, and resource-intensive.
110
110
111
-
Improved Application Performance: Smaller libraries reduce the amount of code that must be loaded, parsed, and executed by an application. This can significantly enhance the startup time and overall performance of the application, especially on devices with limited resources.
111
+
Application Performance: Smaller libraries reduce the amount of code that must be loaded, parsed, and executed by an application. This can significantly enhance the startup time and overall performance of your application, especially on devices with limited resources.
112
112
113
-
Reduced Memory Usage: By minimizing library size, developers can decrease the runtime memory footprint of an application. This is particularly important for mobile and embedded devices, where memory is often constrained. Lower memory usage can lead to fewer system crashes and better multitasking performance.
113
+
Memory Usage: By minimizing library size, you can decrease the runtime memory footprint of an application. This is important for mobile devices, where memory is often constrained. Lower memory usage can lead to fewer system crashes and better multitasking performance.
114
114
115
115
-[UI Library for iOS](https://github.com/Azure/communication-ui-library-ios/wiki/Calling-Composite-Demo-Application-Size)
116
116
-[UI Library for Android](https://github.com/Azure/communication-ui-library-android/wiki/Calling-Composite-Demo-Application-Size)
0 commit comments