Real app screenshot: Soomduu Show
Public web channel focused on links shared from Soomduu Mobile, with open-app/download handoff and direct place URL access.
Accepts shared links from Soomduu Mobile and lands users on web content immediately Supports smart handoff to open the app when installed or route to app download when missing Directly accessible place routes (for example /place/59) for any shop on web Keeps support and policy pages available for public users
Place data is sourced from EVO so shared-link destinations match app-side source-of-truth data
When users receive a shared link, they can open it and reach the target place page instantly on web
Medium to High (depends on module coupling).
Main Challenges
Detail
Users open links such as /place/59 and land directly on the intended place detail. This page exists because built so links shared from mobile can open the exact target place page on web. The primary users are core users and operations team, and its implementation complexity is medium.
Challenges
Detail
If the app is installed it opens directly; otherwise users are routed to download before returning. This page exists because built to continue journeys from web entry to native app with minimal friction. The primary users are core users and operations team, and its implementation complexity is medium.
Challenges
Detail
Users submit name, contact, and issue details through the support form for follow-up. This page exists because built to centralize support intake and reduce fragmented communication. The primary users are core users and operations team, and its implementation complexity is medium.
Challenges
Detail
Users can review policy pages before using account and content features. This page exists because built to clearly communicate rights, responsibilities, and privacy conditions. The primary users are core users and operations team, and its implementation complexity is medium.
Challenges
