A behind-the-scenes look at LinkedIn’s mobile engineering

arstechnica.com

35 pointsvectorbunny2 comments

"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.

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?

Reply on news.ycombinator.com