Game launch guide

These are the standards and feature-specific launch guidelines that apply to Mini Apps. Before launching, be sure to review the details and follow the guide.

If the checklist below is not followed, or if dark patterns are identified, the review will not be approved, and even if they are found after launch, service exposure may be restricted or suspended.

Please note

The items in the launch guide below are continuously being updated.

Access and sound

• The Mini App opens normally to the initial screen within 10 seconds.
• The required sound features such as background music, sound effects, and haptics are applied. It maintains the intended behavior even when silent mode is on or system vibration is turned off.
• If there is sound, users can set it to On or Off themselves.
• When the Mini App is sent to the background, the sound stops immediately.
• When you return to the Mini App from the background, the sound plays normally again.

UX and navigation bar

• The close button in the top-right corner is displayed and works normally.
• It does not intrude into the Safe Area. This includes the iOS Dynamic Island area.
• A bottom sheet does not appear automatically as soon as you enter the Mini App.
• Do not force user actions by using a bottom sheet during specific screen transitions.
• There is a way for the user to exit the Mini App on every screen.
• When you see a CTA button, you can predict what action will follow when it is pressed.
• It does not use links or components to drive traffic to our service or prompt installation of our app.
• In-app ads are not displayed on temporary screens such as intros, loading screens, cutscenes, or popup modals.

User identifier issuance

• The user identifier value is checked and stored, and the game starts normally.
• The user's play records (e.g. ranking, level, stage, etc.) are maintained.
• Even if you exit the Mini App and connect again later, the required data is retained.

Security and stability

• Functions that execute code received from external sources cannot be used. (e.g., eval etc.)
• Methods that manipulate browser history to redirect users to our site cannot be used. (e.g., window.location.replace etc.)
• Server-side rendering (SSR) cannot be used. Only client-side rendering (CSR) or static site generation (SSG) can be used.
• If using WebSocket, use encrypted wss:// connections only. (e.g., Firebase Firestore, Supabase Realtime, etc.)
• API communications should use only encrypted HTTPS connections.
• Sensitive information such as user login information and payment history (Toss Pay, in-app purchases) must be encrypted and stored in the DB.
• We recommend encrypting personal information even when transmitting it from the client to your own server.

Service usage behavior

• Pressing the Android system back button goes back or exits the Mini App.
• The in-game screen is implemented in full screen.
• The set landscape or portrait mode works normally as intended.
• It does not contain content that could be illegal, such as unlawful or sexually explicit content.
• All UI components work normally as intended.
• Interaction responses such as scrolling, touches, and screen transitions are not delayed by more than 2 seconds.
• Device permissions such as location and notifications are requested with user consent first.
• Even if the user does not consent to permissions, the remaining features continue to work normally.
• Network usage does not spike abnormally.
• Memory usage does not spike abnormally.
• A confirmation modal is displayed when exiting the Mini App.
• There are no errors in major service flows such as in-game score tracking and stage clear.

In-app purchases

• When an in-app purchase is being processed, the music playing in the Mini App is paused.
• The in-app purchase order amount matches the amount shown in the Google or Apple payment window.
• The in-app purchase proceeds normally.
• After the in-app purchase is completed and you return to the Mini App, the payment result is reflected correctly.
• If you select Cancel in the in-app purchase window, you return to the order screen.
• If payment fails due to insufficient balance, etc., the user can understand why it failed.
• In-app purchase cancellation is processed normally.
• Users can check the payment history for in-app purchase products.
• Even if you change the device logged in to the Toss app, previously purchased in-app purchase data (items, etc.) is retained.

In-app ads

• When an in-app ad is played, the music playing in the Mini App is paused.
• Comply with the Toss Ads SSP policy. (#)
• Real in-app ads, not test ads, are displayed normally, and there are no cases where they end or crash midway.
• Do not display in-app ads at moments users would not expect.
• In-app ads are displayed normally, and there are no cases where they end or crash midway.
• In-app ads are preloaded. They are not loaded in real time at the moment they play.
• When the in-app ad ends, it returns normally to the Mini App screen.
• After the in-app ad ends, the Mini App music plays again.
• If a reward ad is watched until the end, the reward is granted normally.
• Banner ads are positioned only at the top or bottom.

Share rewards

• The configured share rewards screen is displayed normally.
• When you close the share rewards screen, it returns normally to the Mini App screen.
• When a friend invitation is completed, the reward is granted normally.

Web board games

• Use the adult verification feature integration.
• A customer support inquiry channel is provided so users can make inquiries.
• Users can check the probability information for chance-based items in the game.