chemistrapQ: Few Questions
Hello,
I previously purchased an application quite similar to yours (Fluxbuilder). Frankly, I am generally satisfied with it. It took some time to learn and publish an app initially, but since I mostly use it as a "webview," it hasn't been much of an issue.
However, when I checked out your application, I noticed it offers some different features.
I have a few questions in mind:
Akinola_SwiftSpeed
May 19, 2026A: Hi,
Glad you're checking us out.
Quick answer: yes, we're absolutely better with way more feature and we are more business-feature oriented, with features that will actually get any startup going. So yes, we are superior on both feature depth and publishing workflow. You'll notice it as soon as you build your first app on our platform — wider feature set, cleaner editor, more layouts, real AI App Builder inside the editor (not just templates), and significantly better native build pipeline.
The biggest day-to-day difference: one-click publishing. No Xcode, no Android Studio, no fastlane wrangling. You click Publish, we sign, package, and submit to App Store + Google Play on your behalf. Most webview-style apps you'd normally publish manually become a single button press here.
Happy to answer the specific questions you had in mind — drop them and we'll go through each one.
Push notifications: In my current setup, I configured this via FCM and can use it both through the panel and directly via FCM (unlimited). Additionally, I set up an automation in my current project (WordPress) that bypasses the panel and sends automated notifications directly via the FCM connection. Is this possible with your app as well?
Verified purchaser
Push notifications: yes, fully covered.
1. Panel-driven push (manual). Native admin UI to send one-off pushes, schedule them, target individual users / segments, attach cover images, etc. Same as your current panel, no FCM keys stress, we already prebuilt that workflow.
You can also automate your push notifications or use our API/WEBHOOKS
E-commerce system: I have a concern here. Due to restrictions in the country where I live, I cannot use global payment solutions like PayPal or Stripe. Instead, I integrate local payment gateways or direct bank transfer systems. Would this be a problem within the app? (Please consider both options: building via drag-and-drop or direct webview).
Verified purchaser
Drag-and-drop (native store): We ship Stripe + PayPal + Paystack out of the box, and Direct Bank Transfer is built-in — customer sees your bank details, marks order paid, you confirm manually, with trackable delivery. No global processor needed. Adding a local gateway is on the roadmap; reach out with which gateway and we'll look at it.
You can also use direct webview no issue
Features: I reviewed some features but didn't fully understand them. Can I use the drag-and-drop feature and also receive AI support? Or can I use both webview and drag-and-drop features simultaneously?
Verified purchaser
Yes — both, simultaneously.
Mix drag-and-drop pages and webview pages in the same app, side by side on the same tab bar. AI App Builder works on top of either canvas — go fully manual, fully AI, or blend the two on the same feature.
Email domain: As far as I understand, if I build the app using drag-and-drop, all emails, etc., are sent through your domain. Is this also the case when I build it as a webview? Under which AppSumo plan can we integrate our own email system?
Verified purchaser
Drag-and-drop emails route through our domain by default; custom SMTP (your own domain) needs AppSumo Tier 5 or any Pro/Business plan. Webview keeps using your site's email system untouched.
Caching: Does the app have its own internal caching system? I use the LiteSpeed Cache plugin in most of my projects (which are mostly WordPress-based). Would I experience any issues with this setup?
Verified purchaser
Caching. Yes — the app has its own internal caching layer (asset cache, API response cache, image cache) that works alongside any server-side cache. LiteSpeed Cache on your WordPress backend keeps working untouched; the app just sees faster responses from your origin.