Appushy

Àpèjúwe

Appilix turns your WordPress site into a native Android/iOS app. It gives you a Push Notification API and a user-identity mechanism, but using either from WooCommerce order events requires writing and hosting your own integration code — not realistic for AppilixÌtumọ̀ Yorùbá: ’s largely no-code audience.

Appushy closes that gap. Connect your Appilix App Key and API Key, turn on the order statuses you want to notify customers about, and Appushy handles the rest: identifying which customer to notify, sending the push, and logging what happened — automatically, every time an order changes status.

What Appushy does

• Connects to your Appilix app with your App Key and API Key, and validates them before you rely on them.
• Sends a native push notification when a WooCommerce order reaches a status youÌtumọ̀ Yorùbá: ’ve turned on — Processing, Completed, On Hold, Refunded, and more.
• Sends a native push notification automatically when a student enrols in a Tutor LMS course — free, no Pro license needed.
• Sends a native push notification automatically when someone gets a new direct message via Better Messages — free, no Pro license needed.
• Identifies customers automatically, including guest checkouts, so pushes reach the right device without the customer doing anything extra beyond opening the app once.
• Every triggerÌtumọ̀ Yorùbá: ’s notification lives on one screen — Appushy → Push Automation — where you can see, and toggle, exactly what gets sent and when.
• Logs every send attempt (last 100, with automatic pruning after however many days you choose) so you can see what was actually sent, and why a customer who hasnÌtumọ̀ Yorùbá: ’t opened the app yet didnÌtumọ̀ Yorùbá: ’t receive anything.
• Retries automatically for a few minutes when a customerÌtumọ̀ Yorùbá: ’s device isnÌtumọ̀ Yorùbá: ’t registered with Appilix yet — a common, expected timing gap right after checkout, not a failure.

What Appushy needs from you first

AppilixÌtumọ̀ Yorùbá: ’s Push Notification module requires Firebase to be connected on the Appilix side before any of this works — thatÌtumọ̀ Yorùbá: ’s an Appilix-side setup step, not something Appushy can do for you. See “Before you start” in the pluginÌtumọ̀ Yorùbá: ’s own documentation, linked from the Settings screen, for the full checklist (Firebase project, Cloud Messaging enabled, app rebuilt and reinstalled with the new configuration baked in).

Honest limitations

• Push notifications reach app installs only — not browser visitors. ThatÌtumọ̀ Yorùbá: ’s a different technology (browser push), not something this plugin does.
• A customer must have opened your app and been identified at least once before a targeted push can reach their device. Appushy handles the identification automatically once thatÌtumọ̀ Yorùbá: ’s happened.
• Delivery depends on Appilix and Firebase Cloud Messaging. Appushy logs that it successfully handed a notification to AppilixÌtumọ̀ Yorùbá: ’s API — not that a specific device actually displayed it.
• The Push Notification API is a paid Appilix module, not available on AppilixÌtumọ̀ Yorùbá: ’s free trial.

This plugin bundles the Plus Jakarta Sans, Instrument Serif, and JetBrains Mono typefaces (SIL Open Font License 1.1) for its setup wizard — see assets/fonts/OFL.txt.

External Services

This plugin connects to the Appilix push notification service (https://appilix.com) to send native app push notifications. This is required for the pluginÌtumọ̀ Yorùbá: ’s core functionality — without it, no notification can be sent.

What is sent, and when:

• Your Appilix App Key and API Key (entered by you in Settings) are sent with every request, to authenticate it as coming from your app.
• A customer identity — either the customerÌtumọ̀ Yorùbá: ’s email address or their WordPress user ID, depending on which you choose under Settings → Identify customers by — is sent so Appilix can target the notification to the right device. This is sent both when a customer logs in or completes checkout (to register their identity with Appilix) and with every notification (to target it).
• The notification title and message text, which may include the customerÌtumọ̀ Yorùbá: ’s first name, the order number, and the order total, substituted into the message. This is sent every time an order reaches a status youÌtumọ̀ Yorùbá: ’ve enabled a notification for, and when you use “Send test push.”

This data is sent directly from your WordPress server to AppilixÌtumọ̀ Yorùbá: ’s API (https://appilix.com/api/push-notification and https://appilix.com/api/push-notification-token) — never through any third-party server other than AppilixÌtumọ̀ Yorùbá: ’s own.

AppilixÌtumọ̀ Yorùbá: ’s Terms of Service and Privacy Policy govern how this data is handled once received: https://appilix.com/terms-conditions and https://appilix.com/privacy-policy.