How STYLIGHT went responsive

F716e5f737fcfb03f2cf8d1a184f1dbe?s=47 nonsquared
October 10, 2013

How STYLIGHT went responsive

We don’t decide how people access our websites. They do. And increasingly it’s on mobile devices and tablets.

F716e5f737fcfb03f2cf8d1a184f1dbe?s=128

nonsquared

October 10, 2013
Tweet

Transcript

  1. FINGER FRIENDLY How STYLIGHT went responsive (in 6 weeks). max.mueller@stylight.com

    · @stylight_eng
  2. We want to build the best place to discover fashion

    everyday.
  3. Get inspired by looks created by the community.

  4. Discover thousands of brands and millions of products.

  5. We don’t decide how people access our websites. They do.

    And increasingly it’s on mobile devices and tablets. SUCKED OUR MOBILE EXPERIENCE
  6. 67% 22% 11% Mobile Tablet Desktop

  7. How can we offer a compelling experience on all of

    these devices? SO MANY DEVICES, SO MANY SIZES
  8. ONE SITE TO RULE THEM ALL DEVICE SPECIFIC EXPERIENCES Responsive

    Mobile sites
  9. ONE SITE TO RULE THEM ALL DEVICE SPECIFIC EXPERIENCES Responsive

    Mobile sites * Valid alternative, responsive design isn’t the singular best solution for all circumstances *
  10. WHY RESPONSIVE? Four reasons why we have decided to move

    on with a responsive design for STYLIGHT.
  11. Simplicity. SEO. Conversion from status quo. Speed.

  12. Simplicity. No need for a separate mobile presence, allows us

    to have a single site at a single URL with a single code base and set of files to be used. SEO. Conversion from status quo. Speed.
  13. Simplicity. No need for a separate mobile presence, allows us

    to have a single site at a single URL with a single code base and set of files to be used. SEO. Google officially recommended the responsive design. This is what we want – the leading search engine telling us how to handle your mobile traffic. Conversion from status quo. Speed.
  14. Simplicity. No need for a separate mobile presence, allows us

    to have a single site at a single URL with a single code base and set of files to be used. SEO. Google officially recommended the responsive design. This is what we want – the leading search engine telling us how to handle your mobile traffic. Conversion from status quo. We converted our existing desktop website into a responsive one. There was no need to completely rebuild it. Speed.
  15. Simplicity. No need for a separate mobile presence, allows us

    to have a single site at a single URL with a single code base and set of files to be used. SEO. Google officially recommended the responsive design. This is what we want – the leading search engine telling us how to handle your mobile traffic. Conversion from status quo. We converted our existing desktop website into a responsive one. There was no need to completely rebuild it. Speed. * not really mobile first.
  16. Simplicity. No need for a separate mobile presence, allows us

    to have a single site at a single URL with a single code base and set of files to be used. SEO. Google officially recommended the responsive design. This is what we want – the leading search engine telling us how to handle your mobile traffic. Conversion from status quo. We converted our existing desktop website into a responsive one. There was no need to completely rebuild it. Speed. If designed and developed correctly, a responsive website will improve the overall performance, because it is made for both desktops & mobile devices. * not really mobile first. Source: http://blog.evolvecreativegroup.com/post/2013/07/09/Responsive-Web-Design-vs-Mobile-Site.aspx
  17. OUR WORKFLOW The entire project took 4 people 6 weeks.

  18. Two designers & two developers in the same room

  19. Great designs evolve in collaboration. Kill the waterfall.

  20. Work with code as early and as much as possible.

  21. Handle the visual design upfront in a style guide.

  22. Do not document, do not deliver photoshop files. Prototype it.

  23. Do not document, do not deliver photoshop files. Prototype it.

  24. Do not document, do not deliver photoshop files. Prototype it.

  25. HOW IT TURNED OUT Improved KPIs on all devices, but

    still way to go in our mobile experience.
  26. Before Responsive After Responsive Goal completion rate mobile and tablet

    traffic +24%
  27. Before Responsive After Responsive Average visit duration mobile and tablet

    traffic +36%
  28. None
  29. GRACEFUL DEGRADATION Desktop Down PROGRESSIVE ENHANCEMENT Mobile Up

  30. GIVE IT A TRY! Send us your feedback & get

    in touch with us. max.mueller@stylight.com · @stylight_eng