Soundboks

Problem

SOUNDBOKS - the Danish speaker brand - runs a website, a blog, a webshop and a mobile app. Each surface needed consistent branded UI, but separate codebases meant every component was built and maintained twice.

My role

I was part of the digital team, working across the website, blog and mobile app. My two biggest projects were the design system and the webshop CMS.

Key decisions

For the design system, we built the component library with React Native and React-Native-Web, so a single codebase renders natively on iOS and Android and as regular DOM on the web. One implementation of every component, consistent everywhere.

For the webshop, I drove the selection and implementation of a CMS (evaluating and implementing ButterCMS and Storyblok on top of Shopify) with a clear goal: content editors should be able to create product and landing pages without a programmer in the loop.

Outcome

The shared component library removed the double implementation work between app and web, and the CMS setup moved page creation from the development team to the content team.

Technologies

• React
• TypeScript
• Next.js
• React-Native
• React-Native-Web
• Shopify
• Storyblok CMS
• ButterCMS
• AWS