sriramyadavalli

If Twitter could use common standard like microdata (proposed by w3c), it would probably be a better approach.

The big problem with Twitter product cards is the lack of real time information (ie the data shown to user is crawler dependent). So, e-commerce vendors with dynamic pricing needs (like hotels, airlines) wont use it much. E-Commerce vendors (like Etsy) where users are little less price sensitive have a better shot at using these cards.

IMHO, the hard part in deep linking is connecting existing web app content w/ views inside the mobile app. But, not sure if that can be delivered as a SaaS/proxy service + SDK (since it is too specific to each site).

I am actually developing a service that is a text to speech solution for any app. So, while you travel to work you can listen to ur email/calendar/other data.

May be I am missing something. Isnt Omnilink just detecting the user agent (eg Google/Twitter crawler) and presenting the right content to the crawler? Is there something else to this solution?

Looking at all the client side Android development, seems like the tide has changed

The key issue is that mobile apps tend to be task oriented. A lot of web companies (like FB) are not transitioning into app studios by breaking down a monolithic site into set of mobile apps that deliver a single feature/accomplish a single task.

If the open web were to be redefined along those lines, I dont see why users wont use that.

Nothing wrong with what Google is doing. Google is essentially a consumer (and enterprise) cloud services company that is looking to commoditize (read open source/sell at cost) all other parts of the stack. That includes open-sourcing Chrome/Android, selling Chromecast/Google Fiber at cost.