Applicable scenarios
Potato applet is suitable for products with clear process, quick opening and easy conversational communication. The original website information lists types such as games, shopping, information, videos, music, navigation, travel, learning, financial management, and tools.
Content and Media
News, videos, music and community content.
Life Services
Travel, navigation, reservations and local services.
Trading and Retail
Product display, ordering, payment and order inquiry.
Games and Interaction
Lightweight games, activities, voting and social gameplay.
Learning and tools
Lessons, calculators, queries and productivity tools.
Business Workbench
Entrance to forms, approvals, data viewing and collaboration.
How users discover mini programs
According to the original website help information, users can enter "@app" in the session to search for mini programs, enter the mini program list from the discovery page, or open it through the shortcut entrance provided by the client.
- The name, icon, and introduction should clearly explain the purpose.
- The sharing card should display the source and the specific results after opening.
- Deep pages need to provide a path to return to the homepage or start over.
- Do not induce sharing or licensing through misleading copy.
Lightweight experience design
- The first screen loads quickly and displays core tasks immediately
- Clear touch target, adapt to different screens and security areas
- There are recovery prompts for weak network, timeout and offline status
- Login, authorization and payment are only initiated when really needed
- Provide clear results and return paths after the task is completed
- Avoid copying desktop web pages that cause complicated operations and small font sizes
Performance suggestions
Control the first packet size, delay loading of non-first-screen resources, compress images and cache stable content. Important submissions require repeated click prevention and idempotent processing.
Payment, privacy and security
If the current version of the platform supports payment, the developer must clearly display the product, price, currency, merchant, refund and customer service information, and verify the order results on the server.
- Do not save merchant keys or user sensitive credentials on the front end.
- Payment callback requires signature verification, deduplication and amount verification.
- Describe the purpose before applying for permission and provide an alternative path after rejection.
- The data collected should be minimized and query and deletion methods provided.
- External links, uploaded files and user input all require security verification.
Release check
Product Information
Complete name, icon, introduction, classification and support methods.
Functional test
Covers login, authorization, payment, sharing and abnormal status.
Policy compliance
Prepare privacy instructions, service rules and data deletion methods.
Submit for review
Submit and process feedback according to Potato's current open platform process.