<story><title>Building cross-platform Rust for Web, Android and iOS – a minimal example</title><url>https://www.artificialworlds.net/blog/2022/07/06/building-cross-platform-rust-for-web-android-and-ios-a-minimal-example/</url></story><parent_chain></parent_chain><comment><author>jwells89</author><text>This is cool, but it&amp;#x27;s worth noting that depending on how network-heavy the app in question is it may not be advisable to build the networking portion of an app as part of the shared core.&lt;p&gt;The reason for this is because iOS has a multitude of device specific optimizations built into the native networking stack to my knowledge is opted out of with the usage of cross platform networking. This includes features coalescence of calls across apps to occur when the antenna is already awake (to save power) and transparent management of multi-connection situations (e.g. when the phone has both wifi and cell available). The result is more power used and less fluidity in some situations.&lt;p&gt;I don&amp;#x27;t think this is as much of an issue on Android where third party networking libs like OkHTTP are the norm anyway.&lt;p&gt;With this in mind I believe the best functionality to put in a shared core is generic common logic which does not have platform optimizations.</text></comment>
<story><title>Building cross-platform Rust for Web, Android and iOS – a minimal example</title><url>https://www.artificialworlds.net/blog/2022/07/06/building-cross-platform-rust-for-web-android-and-ios-a-minimal-example/</url></story><parent_chain></parent_chain><comment><author>dylanowen</author><text>I found &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;antoniusnaumann&amp;#x2F;cargo-swift&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;antoniusnaumann&amp;#x2F;cargo-swift&lt;/a&gt; pretty nice for iOS. It uses UniFFI under the hood but automates the other pieces with building an xcode project.</text></comment>