Product Engineering / Public Product
Dcard
Subscription-Based Digital Discount and Loyalty Platform
- Role
- Project Initiator / Technical Product Lead / Solution Architect
- Engineering ownership
- Sole Backend and Web Engineer
- Availability
- App Store + Google Play
From idea to product
A product system connecting users and partner businesses.
Dcard combines subscriptions, digital discounts, offers, and loyalty in a public mobile product. The approved scope includes user discovery, savings, and partner-management workflows at product level.
Initiation
Project InitiatorProduct model
Technical Product LeadRelease evidence
App Store + Google PlayA conceptual view of Sherzod's approved contribution breadth, not a claim of exact project chronology.
Product ecosystem
Users, partner businesses, platform, and mobile product.
The approved product model connects two product sides through the backend and web platform while keeping mobile client implementation as a clear collaboration boundary.
The backend and web platform connects subscriptions, offers, loyalty, users, and partner businesses.
- 01
Product side 01
Users
The public product model includes discovery, offers, savings, and loyalty experiences for users. - 02
Product side 02
Partner businesses
Partner businesses participate through offer and partner-management workflows described at product level. - 03
Client boundary
Mobile product
Dedicated mobile clients connect through server-side contracts and integration boundaries owned on the backend and web side by Sherzod.
My role and ownership
Backend, web platform, and system architecture ownership.
Sherzod's governed role combines project initiation, technical product leadership, solution architecture, and sole backend and web engineering. Mobile implementation remained a separate team boundary.
What Sherzod owned
- 01
Product initiation and technical leadership
Project Initiator and Technical Product Lead are part of the approved role record.
- 02
Solution architecture
Solution Architect is part of the approved role and system-design scope.
- 03
Backend and web engineering
Sole Backend and Web Engineer is explicitly scoped to the backend and web platform, not the mobile clients.
- 04
Server-side integration boundaries
Sherzod defined the server-side contracts and integration boundary used by the mobile clients.
System capabilities
Product capabilities organized around one shared core.
The public-safe capability surface is intentionally limited to subscriptions, offers, partner experience, loyalty, and the mobile experience.
- 01
Capability 01
Subscriptions
Subscriptions are part of the approved high-level digital discount product model. - 02
Capability 02
Offers
Discovery and offer workflows connect the user and partner-business sides of the product. - 03
Capability 03
Partner experience
Partner-management workflows represent the business-facing side of the product. - 04
Capability 04
Loyalty
Loyalty and savings concepts are part of the approved user-facing product purpose. - 05
Capability 05
Mobile experience
The public mobile product integrates with the backend and web platform while retaining a separate implementation boundary.
Engineering model
Product engineering scope
A conceptual view of Sherzod's approved contribution breadth, not a claim of exact project chronology.
- 01Product thinking
- 02Solution architecture
- 03Backend engineering
- 04Web platform
- 05Mobile integration
- 06Public release
Public release
Publicly listed on Apple App Store and Google Play.
The two independently verified store listings are the public evidence surface for Dcard's release.
Publicly listed on Apple App Store and Google Play
What this project demonstrates
Product thinking carried through engineering execution.
- 01
Product-oriented engineering
The approved role spans project initiation, technical product leadership, solution architecture, and engineering execution.
- 02
Backend and web ownership
Sole engineering ownership is explicitly limited to the backend and web platform.
- 03
Cross-client integration
Server-side contracts connected the separately implemented mobile clients to the platform.
- 04
Multi-sided product modeling
The product brings users and partner businesses together through subscriptions, offers, savings, and loyalty concepts.
- 05
Public release evidence
Dcard is publicly listed on both the Apple App Store and Google Play.
Public evidence
Inspect the public product listings.
The two independently verified store listings are the public evidence surface for Dcard's release.