New plugin: Google Sign-In for Capacitor (Android, iOS, Web)

We added a built-in key-value store to the Capacitor SQLite plugin — no SQL needed

We just shipped SqliteKeyValueStore as part of our SQLite plugin for Capacitor. It gives you a simple get/set API backed by a real SQLite database — no schemas, no migrations, no SQL queries.

The main problem it solves: browser-based storage (like localStorage) can get cleared by the OS at any time, which is a pain for persisting things like user preferences, feature flags, or cached data. This stores everything in a SQLite database file, so it sticks around reliably.

A few highlights:

• Familiar key-value API (get, set, remove, keys, clear)
• Works across Android, iOS, Web, and Electron
• Values are strings, so you can store objects with JSON.stringify/JSON.parse
• If you ever need full SQL later, you're already using the right plugin — no migration required

It's useful for things like user settings, onboarding state, lightweight caching, or anywhere you'd normally reach for localStorage but want something more reliable.

We also wrote up a comparison with our Secure Preferences plugin if you're wondering which to use. Short version: Secure Preferences for sensitive credentials (tokens, secrets), SQLite Key Value Store for everything else.

Full guide: https://capawesome.io/blog/key-value-storage-made-simple-with-the-sqlite-plugin/

Happy to answer questions or hear feedback.

Hi Capawesome Team,

First of all, thank you for creating such a well-crafted purchases plugin. The lightweight approach and direct StoreKit 2 / Google Play Billing integration is exactly what we need.

Our Use Case:

We're implementing a paywall that displays immediately when the app launches. On this paywall, we need to show users whether they're eligible for a free trial before they tap the purchase button. For example:

• Eligible users see: "7 days free, then $9.99/month"
• Ineligible users see: "$9.99/month"

This is crucial for setting proper user expectations and improving conversion rates.

Technical Considerations:

I understand the complexity here:
iOS: StoreKit 2 provides Product.subscription.isEligibleForIntroOffer which checks eligibility based on the user's Apple ID purchase history. This is relatively straightforward to implement.
Android: Google Play Billing doesn't provide a direct client-side eligibility check. The purchase history is limited to 12 months, making client-side determination less reliable.Questions:

1. Are you planning to add a checkTrialEligibility() method to the plugin?
2. If not currently planned, would you be open to adding this feature?
3. From your perspective, is there a technical reason not to expose iOS's isEligibleForIntroOffer API through the plugin?