Re: Deep linking

Thanks Dom and Leandro for these inputs and insights.I have actually been recently reading up on Deep Linking topics myself to find out about practical and readily ways to implement or enable such capabilities for Apps.I did lately encounter a challenge pertaining to the problem of app linking while browsing apps on my mobile and before I thought too long, I realized this problem was already a known one with solutions being envisioned and worked on.I believe Mobile Web Deep Linking  offers the potential to attaining a more versatile and robust web that provides maximum opportunities for better e-commerce and customer engagement in the ads space. However the the most significant hurdle and challenge for it as a new technology method is the question whether the siloed landscape of companies, startups and competing open-source frameworks can coalesce. Developer adoption is the next phase in making mobile deep links not only more intuitive, but ubiquitous across platforms. And therefore to achieve that, developers need tools to simplify the process and a universal standard of common and best practices and methods to unify it. So standardization is a huge factor in the forward movement and widespread adoption of this new web trend and methodology.Besides solution approaches offered by Google, Facebook, etc...there are a few start-ups that also jumped on the band wagon also looking at implementation and standardization approaches. To mention a few, we have BranchMetrics, URX, Deeplink.me, Quixey... etc... Here are a few links that can give you a bit of idea and insight:https://branch.io/��
http://urx.com/
http://mobiledeeplinking.org/
https://deeplink.me/
http://www.nytimes.com/2015/01/06/technology/tech-companies-look-to-break-down-walls-between-apps.html?emc=edit_tu_20150106&nl=technology&nlid=66768929&_r=0

So I believe it will be a good effort and  initiative for a community in W3C to look into this new trend and also work with various partners in order to keep a consolidated set of methods, practices and recommendations and also guide further development in this subject matter.Let's follow up and see how that goes.
Thanks,
Souma B-W
804.919.2787
www.soumaonline.net
www.livelypulse.com 

     On Tuesday, January 6, 2015 7:37 PM, Leandro Melo de Sales <leandro@ic..ufal.br> wrote:
   

 Hi Natasha, Dom and others,
    Particularly, I really like the idea. In my case, I used to develop my own solution to communicate different apps when needed in a mobile context, but again, with no standardization and open way to allow apps from other vendors to communicate with the mine and vice-versa. In this context, I'm confident to go through this topic and discuss about it further.
    I have some use cases that I can share in a proper moment considering that we will go through on this topic. Please, count on me in contributing efforts in this space.
Best,
Leandro.

--
DSc. Leandro Melo de Sales
Institute of Computing (IC) at Federal University of Alagoas (UFAL), Brazil
CEO at Pervasive and Mobile Computing Laboratory (COMPELab.org / IC)    
"The warrior is strong in loyalty, intensity, determination, initiative, persistence, courage and willpower. The warrior is light in the soul, self-trust and compassion. The warrior is often called to take the front when other cowardly make a step backwards. There are warriors on the battlefields and in everyday life."
2015-01-07 0:18 GMT-03:00 Natasha Rooney <nrooney@gsma.com>:

Thanks for this Dom!

Everyone: happy new year! Please read Dom’s post below and let us know if
you have any thoughts.
Dom: should we reach out to the Quixey, Google, Facebook guys? Let me know
and we can get them involved too!

Natasha

Natasha Rooney | Web Technologist | GSMA | nrooney@gsma.com | +44 (0) 7730
219 765 | @thisNatasha | Skype: nrooney@gsm.org

Tokyo, Japan







On 1/6/15, 19:44, "Dominique Hazael-Massieux" <dom@w3.org> wrote:

>Hi,
>
>In the past few months, several efforts have emerged to try to make
>native apps get some of the benefits of the Web (inter-linking), as well
>as to make them more integrated in the Web (seamless transition between
>browser-based and native-based views of the Web).
>
>Google has app indexing:
>https://developers.google.com/app-indexing/webmasters/app
>Quixey has appURLs: http://appurl.org/
>Facebook has AppLinks:
>https://developers.facebook.com/blog/post/2014/04/30/app-links
>http://applinks.org/
>URX has omnilinks
>http://blog.urx.com/urx-blog/omnilinks-app-links-and-the-state-of-mobile
>
>These efforts have also received attention from the press:
>http://recode.net/2014/10/28/how-deep-linking-could-fix-mobile/
>http://www.nytimes.com/2015/01/06/technology/tech-companies-look-to-break-
>down-walls-between-apps.html?ref=technology
>
>Given the number of competing proposals in this space, and given they're
>only as useful as they get widespread, it feels to me this space is
>probably ripe for some standardization effort, or at least
>pre-standardization.
>
>It's also an interesting twist to the usual “native vs Web” — it is
>closer to “native ♥ Web”, with benefits for all.
>
>I'm looking for feedback on the topic, and potential interest in
>contributing efforts in this space.
>
>Follow up actions could be a community group, or even a workshop if we
>feel this type of topic requires broader visibility from the community.
>
>Thanks, and happy new year to all!
>
>Dom
>
>

This email and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this email or call +44 207 356 0600 and highlight the error.