Unified POS System

Why is it important?

Clover POS system is built as app-based ecosystem, each developed independently, which makes it feel like they come from different companies due to a lack of cohesive design and unified code.

This leads to increased tech debts and quadruple the cost of design, development and maintenance. Additionally it complicates testing new features with users because of the disparate code base.

What we want to accomplish

  • Reduce development and maintenance costs.

  • Have one reliable code and experience that works on any form factors.

  • Ensure consistent and familiar behaviors wherever merchants use Clover ecosystem.

  • Develop clean and scalable technical architecture to make testing and updates easier.

What I did

  • Advocated combining experiences, code, and design by creating and presenting a complete concept.

  • Led and guided designers in developing this idea into concrete details.

  • Build a strong network of allies in company leadership and engineering team who have the skill set to turn the concept into prototype, and then into a real product.

  • Worked with the design system team to extend our web design system into one for Clover hardware OS.

Using framework to build real products

Compact, kiosks, phone and tablet app have consistent Clover experience that leverage the same design components.

Clover Compact is the first Clover POS device that meet the goals of Unified POS Framework. It was built with consolidated code base, using design components, and focuses on primary workflows.

Impacts

Engineering team consolidated 5 code base to one based on this framework that cut development and maintenance time by 75% and reduced engineering cost by upward of quarter of a million USD annually.