Simple, flexible licensing
Ipinapakita rito kung ano ang supported ng app ngayon at kung ano pa ang kailangang i-confirm bago ilabas ang prices at purchase terms.
Launch blocker: the supplied Android project uses signed offline activation. It does not configure Google Play Billing, SKU IDs, prices, 30-day or 12-month expiry periods, or restore and upgrade behavior.
License options requested
Exact availability, peso pricing, access duration, and included features need to match the live Android product configuration before launch.
Launch detail pending: Google Play Billing products, prices, and the official store listing are not present in the Android project. We’ll publish license instructions once verified.
1 Month
Exact access period not published
Requested license option. Availability, purchase flow, exact period, and terms need confirmation.
1 Year
Exact access period not published
Requested license option. Availability, purchase flow, exact period, and terms need confirmation.
Lifetime
Exact access period not published
Requested license option. Availability, purchase flow, exact period, and terms need confirmation.
The Android app currently validates signed offline license codes. Google Play Billing products and these three license options are not configured in the app source.
Current licensing behavior
These statements are based on the current activation and data-storage implementation.
The app source has no in-app billing implementation. Google Play purchase products are not configured.
There is no subscription or automatic renewal code in this project. The future commercial purchase model still needs confirmation.
Current signed license codes are validated against the device fingerprint and stored locally.
The verifier accepts an expiry value of zero. What ‘lifetime’ includes beyond no expiration is not defined in the current source.
New installs ask for the device ID. An offline signed code is issued for that device and entered in the app. Existing installs with a saved business database are grandfathered by the current startup logic.
An expired code fails local validation and the app returns to activation. Shop data remains in the local app database unless app data is cleared or the app is uninstalled.
The current project does not implement Google Play purchase restoration, upgrades, or account-based entitlement lookup. Ask support for help with current offline activation.
Bago pumili
Ang mga sagot ay base sa current app implementation. Kailangan pang i-review ang commercial license policy bago ito i-publish.
Basahin ang license terms draftThe current Android source does not implement recurring subscriptions or Google Play Billing. New installations currently require a signed offline activation code. The published commercial purchase model still needs confirmation.
The current app contains no automatic renewal or recurring billing code. Google Play one-time products are not configured in this repository, so we cannot describe a Google Play billing flow yet.
Those three product names and prices are not configured in the Android project. The current verifier supports a signed code with an expiration timestamp, including a no-expiry value, but exact product periods and terms are not published here.
For a new installation, the app displays a device ID. An AquaWash provider issues a signed offline license code for that device, and the user enters the code in the app. The code is checked locally.
The app treats an expired code as invalid and returns to its activation flow. Existing database records remain stored locally unless app data is cleared or the app is uninstalled. Access to the app requires valid activation.
Current offline activation codes are tied to a device fingerprint derived from the app package identity and Android ID. A code issued for one device will not validate on another device.
The app source does not implement Google Play purchase restoration or license upgrades. Current activation is device-bound and issued offline; the provider contact and transfer process have not been published yet.
A refund policy for commercial license purchases is not published in the repository. Google Play refund procedures cannot be promised until Google Play products are configured. The app owner still needs to publish a purchase support contact and refund process.
For your everyday operations
Mas madaling mag-manage ng orders, payments, at daily operations kapag organized ang business records.
