Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't call it Mobile #9

Open
jorabin opened this issue Jan 19, 2014 · 4 comments
Open

Don't call it Mobile #9

jorabin opened this issue Jan 19, 2014 · 4 comments

Comments

@jorabin
Copy link

jorabin commented Jan 19, 2014

Call it "Contextual and Cross Channel Web Best Practices" (C3W)

@paulirish
Copy link

"multi-device" or "cross-device"?

@mathiasbynens
Copy link

Just call it “best practices”.

@jorabin
Copy link
Author

jorabin commented Jan 21, 2014

Assuming:

“Multi-device” refers to the ability to deliver a representation that provides at least a “functional user experience” and preferably a “harmonized user experience” in a range of “delivery contexts” (terms chosen from the still unpublished http://www.w3.org/TR/di-gloss/ )

And “cross-device” refers to the ability of a user meaningfully to start, continue and complete tasks across a number of distinct delivery contexts?

The distinction perhaps being that multi-device is a server centric view and cross-device is a user centric view?

I’m going to argue that “device” is a bit too laden with implications about “phone” “tablet” etc and that thinking forward to a world of distributed clients and servers (IoT and Wearables etc. where it’s uncertain that client and server exist at a single point in the network) it’s preferable to my mind to think about delivery context and "access mechanism” (also from http://www.w3.org/TR/di-gloss/).

That’s why I propose Contextual and Cross Channel - contextual to encompass the idea of user preferences as well as the characteristics of the channels they have chosen (or been forced) to use in the course of carrying out a task.

Not to mention that it appeals to me to have the initialism C3W for Contextual and Cross Channel Web, because it’s W3C backwards.

@jorabin
Copy link
Author

jorabin commented Jan 21, 2014

Re "Just call it “best practices”. I agree with the sentiment in the sense of “The Web is /for/ Mobile, Stupid!” however, the existence of the Web and Mobile Interest Group is predicated on the assumption that a significant constituency needs to be alerted to a change that happened a while ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants