斑斑笔顺 - 小学写字正确笔顺 Support
潇和时代Summary
If you encounter any issues while using Banban Bishun (a Chinese character stroke-order learning app with textbook sync), please contact us through the channels below. We usually respond within 1-3 business days. To speed up troubleshooting, please include your device model, OS version, app version, screenshots, and clear reproduction steps. If the issue relates to grade/textbook content, stroke practice, printing, or ads, please mention the feature you used (e.g., Home, Daily Practice, Favorites, Print) and the character or textbook version involved.
Contact
- Email: houzqiang@gmail.com
- Phone: 18600019451
- QQ: 568049509
FAQ
1. How long does it take to receive a response?
We usually respond within 1-3 business days. Response time may be longer during peak periods.
2. What information should I include when reporting an issue?
Please include:
- Device model (e.g., iPhone 15, iPad Air)
- OS version (e.g., iOS 18.x)
- App version
- Screenshots or screen recordings
- Clear reproduction steps
- If related to learning content: character(s), textbook version/grade, Simplified vs Traditional UI
- If related to features: Home stroke view, Daily Practice, Custom Practice, Favorites, Print/Export, Classical Literature, etc.
3. Why is the first launch or data loading slow?
On first launch or after an update, the app prepares local textbook and stroke-order data (large assets). This can take a while and is expected. Ensure enough free storage (1GB+ recommended), close heavy background apps, and try again. If it stalls, force-quit and reopen, or use Wi-Fi (app open ads require connectivity).
4. What should I check first if a feature is not working?
Please check in this order:
1. The app is up to date (from the App Store)
2. Enough free storage; force-quit and reopen the app
3. Network is stable (app open ads and some pronunciation assets need connectivity)
4. If you see usage-limit prompts: follow in-app share/unlock instructions, or contact us below
5. Restart the app; if it still fails, try changing the in-app language once (helps us match UI strings when investigating)