- The web is its own medium; a medium defined by its fluidity.
- It’s available on any device, one web. As long as we don’t break it.
- One web is:
- One content
- One url
- One team
- One release schedule
- One codebase
- One web sounds a lot like responsive.
- The phrase adaptive is magic.
- No one seems know what adaptive means.
- An m-dot site is dedicated site served to mobile users, but it’s easy to server the wrong content.
- Adaptive is often used to means: serves something different to different devices. It may mean
- A limited of media queries where the width jumps rather than fluidly grows
- Serving something different, the url remains the same but the content is served differently
- Karen McGrane prefers the latter definition.
- Adaptive content is server side, the server detects the device and serves something different.
- Google is the one company most invested in your site serving the same content at the same url all the time.
- If the home page is political, serve a different home page and keep the rest of the site responsive. Do it, go adaptive on the home page.
- Adaptive doesn’t need to be per page, it can be per component. Fidelity used two versions of markup for adaptive tables based on the screen site.
- Don’t get the server involved with content when it’s a client side problem.
- Karen McGrane has spoken about adaptive for five years, since discussing COPE.
- There is a great value in storing chunks of granular content rather than massive blobs.
- It makes it easy for people to conclude they should be targeting different users with different content.
- One way of targeting is based on the users device.
- There are other ways. Context: information that can be gleaned from the devices sensors, the time, location, velocity, barometer, temperature.
- Think about this, when does it make sense to serve different content based on the device vs different content based on the users context?
- Device: support pages based on the users operating system.
- Even based on device selection, prioritise the content rather than exclude the content. An iOS user may be helping their Android using friend.
- Often people make assumption to adapt on device that are stretching it’s suitability, to assume the input mechanism, for example.
- Microsoft think there is no difference between what mobile & desktop users desires.
- Karen’s definition of context (device sensors) are the closest we can get to guess the users context.
- Modern hearing aids can switch to car mode when travelling over 10mph. This is a good but imperfect solution (could be a human canon ball).
- Restaurants can be displayed according to the user’s location, this is a good contextual cue.
- Language may not be a good contextual cue for language, this can be flawed – visitors arriving in a foreign country.
- Device detection is flawed, there is no correlation between being away from home and using a mobile device.
- Device type will always be the least reliable form of estimating context.
- Expedia found that responsive was better than context targeting. A travel company.
- Adaptive and responsive are not in competition, they work together. RWD will solve 95% of your problems, adaptive may cover the remaining 5%.
Leave a Reply