Skip to content

chore(example): remove legacy Offerings flow from sample app - #462

Merged
smejl merged 1 commit into
developfrom
chore/remove-offerings-from-sample
Jul 19, 2026
Merged

chore(example): remove legacy Offerings flow from sample app#462
smejl merged 1 commit into
developfrom
chore/remove-offerings-from-sample

Conversation

@smejl

@smejl smejl commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Context

Offerings are being sunset in favor of Remote Configs. This PR removes the legacy Offerings flow from the sample (example/) app so it no longer demonstrates a deprecated API. SDK code is untouched.

The sample app already sources its product list from Qonversion.getSharedInstance().products() (Products screen), so no functionality is lost.

Migration guide: https://documentation.qonversion.io/docs/migrate-offerings-to-remote-configs

Changes (example/ only)

  • Delete example/lib/screens/offerings_screen.dart and its import + /offerings route in main.dart
  • Remove offerings state (field, getter, setter) from app_state.dart
  • Remove the Offerings entry from the main menu in main_screen.dart

Notes

  • Minimal diff; no changes to SDK sources.
  • dart analyze was not run — no Flutter/Dart toolchain available in this environment. grep -rni offering example/lib returns no remaining references.

🤖 Generated with Claude Code

Offerings are being sunset in favor of Remote Configs. The sample app now
sources the product list solely from Qonversion.getSharedInstance().products().

- Delete offerings_screen.dart and its route/import in main.dart
- Remove offerings state (field, getter, setter) from app_state.dart
- Remove the Offerings menu entry from main_screen.dart

See: https://documentation.qonversion.io/docs/migrate-offerings-to-remote-configs

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@smejl
smejl merged commit d9ce9d9 into develop Jul 19, 2026
1 check passed
@smejl
smejl deleted the chore/remove-offerings-from-sample branch July 19, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant