gmi.software
Services

Start with the outcome you need to achieve.

Explore all services
Core areas
Mobile appsApp takeover, development and iOS/Android releasesOnline stores & B2B platformsOnline store development and integrations with business systemsIntegrations & back officeERP, inventory, payments and APIs
Start hereMobile app code auditBefore the first release or when a live app needs repair
Complementary services
App maintenanceSLA, monitoring, stability and continuous improvementE-commerce mobile analyticsFunnel measurement and data-led decisionsAI & automationFrom workflow and business case to productionProduct Discovery & DesignScope, prototype and delivery planWorkshops & estimationRisks, decisions and fixed-price scope
Not sure where to start?Book a short consultation
Projects

Explore products shaped by clear decisions and measurable outcomes.

All case studies
Delivered products

Case studies

Interfaces, scale and delivery outcomes
Świat KsiążkiMobile loyalty programme and product catalogueSFDCommerce, loyalty and everyday motivationSTS / Solarts3D solar installation configurator
Looking for inspiration? Explore the app ideas library
Technologies

We choose the stack around the product, scale and risk.

Explore the full technology stack
Featured
MobileReact NativeScalable iOS and Android productsMobileExpoFaster releases and updates for React Native apps
Web & commerce
Next.jsReactTypeScriptMedusaJS3D configurators
Backend & cloud
Node.jsNestJSPostgreSQLDockerAWS
Quality
PlaywrightMaestro
Tools

Estimate costs and organise decisions before a call.

3 free tools
App cost estimateEstimate scope and budgetOpen toolE-commerce AI adviserMap decisions, risks and optionsOpen toolE-commerce TCO calculatorCompare SaaS and custom over 5 yearsOpen tool
Already have a result or brief?Discuss your outcome
Company

Meet the people, working model and principles behind GMI.

About usAccountability, history and proofCareersHow we work and open applicationsContactNew projects, support or partnershipsBlogNotes on app and commerce development
ENGet in touch
Services
Mobile appsOnline stores & B2B platformsIntegrations & back officeStart hereMobile app code auditApp maintenanceAI & automationAll services
Projects
Technologies
React NativeExpoNext.jsNode.jsFull technology stack
Tools
App cost estimateEstimate scope and budgetE-commerce AI adviserMap decisions, risks and optionsE-commerce TCO calculatorCompare SaaS and custom over 5 years
Company
About usCareersContactBlog
Get in touch
Back to blog
Product design
Published: July 29, 2026
9 min read

Product design vs product development: responsibilities and delivery order

Product design defines the problem, experience and behaviour of a solution. Product development covers building, releasing and operating the full product. Both disciplines need one shared loop.

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

In brief

Product design defines the problem, experience and behaviour of a solution. Product development covers building, releasing and operating the full product. Both disciplines need one shared loop.

Product design defines the problem, experience and behaviour of a solution. Product development covers building, releasing and operating the full product. Both disciplines need one shared loop.

Product design asks what to build and why

Product design combines user research, process modelling, information architecture, interaction, language and visual treatment. Its output is not only a set of screens; it is a validated set of assumptions and a description of how the user reaches the goal.

A product designer needs business and technical context. A beautiful solution that cannot fit the budget or connect to real data is not good product design.

Product development owns the working system

Product development covers architecture, implementation, testing, release, analytics, security, maintenance and iteration. The team owns not only the visible interface but also data, integrations, roles, errors and operating workflows.

Development starts before the first commit. Engineers should join discovery when feasibility, integration or cost can change the product direction.

One loop instead of document hand-offs

The strongest model brings designer, engineer and business owner around the same risk. The team designs a small flow, tests it with users and technology, ships it, measures the outcome and returns to the next decision.

  • Discovery: problem, process, data and risks
  • Design: flows, content, states and prototype
  • Technology: PoC for technical unknowns
  • Delivery: a small working scope
  • Measurement: user behaviour and business outcome

When each discipline matters most

If the problem is an unclear vision or workflow, start with product design. If the direction is validated but no stable system exists, development becomes dominant. A new product almost always needs both; only their intensity changes by stage.

Related reading

  • Product design and UX/UI

    Discovery, flows, prototypes and validation before expensive implementation.

  • Prototypes and MVPs

    A bounded scope, validation of the critical risk and a plan for the next iterations.

  • Discovery–Design–Technology process

    One decision loop connecting business, design and technology.

Content updated: July 29, 2026

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

Mikołaj Lehman is the CEO and founder of GMI Software. On the blog, he covers decisions around mobile apps, ecommerce and digital product delivery.

  • Mobile apps and React Native
  • Headless and B2B ecommerce
  • MedusaJS
  • Digital product delivery

Google Preferred Sources

See GMI more often in Google

Add gmi.software as a preferred source. Google may highlight our new articles more often in Top Stories and supported AI experiences.

Share article:

Related articles

Product design

What is a mockup, and why should you create one before coding?

A mockup shows product layout, hierarchy and visual direction before expensive implementation starts. This guide explains the difference between sketches, wireframes, mockups and prototypes, and when each one is enough.

→
E-commerce

Multi-vendor marketplace on MedusaJS: what you need to design

Vendor model, data and permission isolation, offer publishing, per-vendor orders and the limits of the Medusa v2 core. Ends with the criteria for building the module yourself or adopting a ready-made one.

→

Let’s discuss your project.

Tell us what you need. We’ll suggest the next step.

[email protected]
gmi.software Sp. z o.o.ul. Jana Heweliusza 11 / 819
80-890 Gdansk, Poland
Rated 5.0 out of 5 on Google5.017 client reviews on Google
© 2026 gmi.software Sp. z o.o.
Privacy PolicyTerms