A behind-the-scenes look at LinkedIn’s mobile engineering
arstechnica.com
A behind-the-scenes look at LinkedIn’s mobile engineering
1–3 of 3 posts
Re: A behind-the-scenes look at LinkedIn’s mobile engineering
#2"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.
Re: A behind-the-scenes look at LinkedIn’s mobile engineering
#3"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…
I assume they knew about this technique, since it is how phonegap and others work.
Perhaps they actually are using this technique, and the reporter got confused?