Add Ionic Capacitor example app

[jennantilla]

Description

One Line Summary

Add Ionic Capacitor example app

Details

Motivation

Unlike many of our other repos, Cordova does not have an integrated example app. This means that currently, any testing for the SDK must be done by linking/unlinking the changing repo to a separate standalone app. The demo apps provided in the README are limited in terms of method functionality and are out-of-date (Player Model). Further, since test apps are not directly linked to the SDK, a fair bit of set up is required on the tester side to get started.

Adding an integrated example app with User Model methods and an automatic linked dependency to the SDK will allow for a seamless test experience for further Cordova SDK development.

The Ionic Capacitor React framework (vs. Cordova) was chosen due to its more widespread use from our customers as well as its enhanced native functionality and robust product support. Additionally, since this example app uses React, updating it will be very similar to the existing React Native app, which will aid in app maintenance and reduce context switching while testing between the two SDKs.

Scope

A new directory, /examples has been added to the Cordova SDK.

From this directory, the example app can be opened by running:

ionic capacitor run android

ionic capacitor run ios

Testing

Manual testing

Functional testing of the added method buttons was completed on both an iOS 17.2 simulator as well as an Android 14 Emulator.

iOS

Android

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is 

[nan-li]

Awesome!