Ionic Support

[stefashkaa]

Feature Title

Ionic Support Strategy: Documentation-First vs Dedicated Package

Description

Parent: #79

Define and implement the Ionic support path.

We need a clear decision whether Ionic should be supported via integration docs only (using existing web packages) or via a dedicated Ionic package.

Use Case

Ionic apps (Angular/React/Vue + Capacitor) need predictable guidance for using phone-mask with mobile-friendly UX and consistency.

Proposed Solution

Phase 1 (required):

• Publish official Ionic integration docs for:

  • Ionic + Vue (@desource/phone-mask-vue)
  • Ionic + React (@desource/phone-mask-react)
  • Ionic + Angular (@desource/phone-mask-ng) - Depends on Design Angular version of phone-mask #9

• Include mobile-specific recommendations:

  • input mode/type
  • keyboard behavior
  • country selection UX

Phase 2 (decision gate):

• Evaluate whether a dedicated package (@desource/phone-mask-ionic) is needed based on:
  • API gaps
  • DX friction in docs-first approach
  • maintenance cost vs value

Alternatives Considered

• Ship dedicated Ionic package immediately (higher maintenance now).
• Keep unofficial community examples only (inconsistent onboarding).

Examples from Other Libraries

• https://github.com/ionic-team/ionic-framework
• https://github.com/iamstevendao/vue-tel-input
• https://github.com/bl00mber/react-phone-input-2