Re:A behind-the-scenes look at LinkedIn’s mobile engineering
by danielschwartz on Tuesday October 02, 2012 @12:37PM
(#4602822)
"The company embedded an extremely lightweight HTTP server in the application itself. The HTTP server exposes native functionality through a very simple REST API that can be consumed in the embedded HTML controls through standard JavaScript HTTP requests"
As someone who has built a bridge between the WebView and iOS, why would you not use the native app url scheme (ex. linkedin:///goTo?storyId=1) and listen for them within the app? Even a lightweight HTTP server seems like serious overkill for this.
As someone who has built a bridge between the WebView and iOS, why would you not use the native app url scheme (ex. linkedin:///goTo?storyId=1) and listen for them within the app? Even a lightweight HTTP server seems like serious overkill for this.