Replies: 2 comments 7 replies
-
|
This is a valid documentation organization issue. Problem: Discount types are Android-specific but split across two documentation pages:
Why this matters:
Action needed:
This is a straightforward documentation refactoring that improves information architecture. 🤖 Generated by gitdog.dev · Have more questions? Tag |
Beta Was this translation helpful? Give feedback.
-
|
@dfabulich Thanks for the suggestion! After reviewing both pages, I'd like to share why I think the current structure makes sense: Different Content Types The UI implementation examples (React Native, Kotlin Compose, Godot) Different Product Types Discounts page: Covers one-time purchase offers (Google Play Billing Library 7.0+) Discoverability Developers looking for "how to implement discounts" would naturally look in Features, not Types. The current placement matches user expectations. Alternative If you'd like, I could add a cross-reference link from the Android Types page to the Discounts feature guide for better navigation. Let me know if that would be helpful! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
https://www.openiap.dev/docs/features/discount is a separate page from https://www.openiap.dev/docs/types/android but I see no clear reason why. It's a bunch of Android-specific types; those should all be grouped together.
Beta Was this translation helpful? Give feedback.
All reactions