Mobile-First or PWA? Basketly's Product Design Trade-off for Grocery Delivery

Tech · 4 min read

Basketly launched in three cities with an initial web app built quickly for checkout and inventory sync. As downloads grew, leadership debated whether to invest in native apps immediately or keep iterating the PWA. The product team applied a decision framework: measure core metric sensitivity to platform features (push, offline), score engineering cost, and estimate user acquisition lift.

The result was a staged approach: keep the PWA as the canonical experience while investing in a lightweight native shell for top-tier markets to deliver push notifications and smoother payments. The design team focused on parity of the critical path—search, cart, and one-page checkout—so that switching channels wouldn’t fragment analytics or UX.

Early returns are promising: markets with the native shell saw a 10% lift in repeat order rate (driven by timely push messaging), while the overall PWA improvements lowered engineering overhead and increased test iteration speed. Basketly’s approach highlights a pragmatic trade-off: platform investments can be incremental when product design constrains differences to the core funnel.