[Tech inquiry] (beta) — Key Questions to Validate Adoption ✅
Hi Noor Khan and team 👋 Noor Khan
I’m David from Human Excellence Plus (HE+). We already launched a production app using a Web2Native wrapper and we’re transitioning to Capacitor. In parallel, we’re seriously evaluating Appza(October launch). I’m excited to test the beta launch yesterday (I know this is no the white label app), but I’m hitting several errors and I haven’t been able to sync my Fluent Community with the app yet—could someone please help me get connected?
Our use case relies heavily on deep links and especially live push notifications (without “live” push, the app doesn’t work well for us). Could you clarify the following?
2) Authentication & Sessions
• Primary mechanism? (WP cookies / JWT / SSO).
• Can you extend sessions to avoid frequent logouts?
• Support for Face ID / Touch ID as quick re-entry?
3) Push Notifications (critical)
• Push engine: native (APNs/FCM), your own, or OneSignal? Do you support External User ID for segmentation (FluentCRM/Community tags)?
• Deep links from the notification to posts/courses/spaces?
• Actions, images, silent push, and badge count?
• Custom notification sounds per channel (iOS/Android)?
• No-code segmentation (spaces, courses, tags), scheduling, and basic logs/metrics?
• GDPR consent and per-device opt-out?
4) Deep Links & URL Rules
• Universal/App Links + URL scheme with web fallback?
• A rules engine for Internal vs External (patterns/regex) to decide in-app vs external browser?
• Logout flow that redirects to /heplus/ without exiting the app?
5) Container UI/UX
• Splash with loader: do you allow an intro video with sound? (I know Apple can be strict—just confirming options.)
• Status bar control + system light/dark mode compatibility.
• Orientation controls: portrait on phones; option for portrait/landscape on tablets.
• No-internet screen.
• Haptic feedback support.
6) Media & Files
• Bunny.net Video Player: SDK inside the app? PiP, background audio, DRM/basic protection?
• Persistent audio player across navigation. This is very important for our community because we deliver online courses.
• PDFs: native render / download to sandbox / external open / share sheet / offline for key docs.
• Media caching policy for heavy content.
8) Engine / Performance (short)
• Which engine do you use (WKWebView on iOS, Android System WebView, or custom)?
• Basic capabilities to know: hardware video acceleration, sensible caching/preloading for web/app content.
9) Migration (if we proceed)
• If we go with Appza, how would you handle migration from our Capacitor/Web2Native setup so we keep:
• our Internal/External URL rules,
• deep links,
• splash/loader/status-bar behavior, and
• push (OneSignal + External User ID).
Thanks a lot for the guidance—and if possible, please share a technical contact so I can resolve the beta sync issue quickly. Looking forward to putting Appza through its paces! 🙌
Hello David Badilla Salazar Thank you for the detailed post/questions. Please email me at [email protected] , will be easier to answer and communicate through email on these.
I saw your post earlier on Lazycoders' community and requested the same
Noor Khan Hi Noor, thank you so much for the quick response! 🙏
I’ve just emailed you at [email protected] with our details, the beta sync issue, and the key questions.
Happy to continue the technical discussion by email and circle back here with any updates that might help others.
Looking forward to testing Appza further—thanks again!
Hello, David Badilla Salazar
Is your site https://www.webtonative.com/? If so, I’ve noticed an issue with it. The problem is that the app FluentCommunity conflicts with the Pull to Refresh feature. As a result, scrolling down the page works fine, but when scrolling up from the bottom, the page reloads unexpectedly. I hope you can help resolve this issue.
Thank you.
Arif Kazi Hi Arif, sure!
You’re right—there’s a conflict between FluentCommunity’s own refresh/scroll handling and the wrapper’s Pull-to-Refresh. Two refresh layers cause the unexpected reload when scrolling up (much more noticeable on Android than on iOS).
What worked for me:
- In the Web2Native build config, I disabled Pull-to-Refresh entirely.
- I let FluentCommunity handle its own refresh logic.
- Rebuilt and cleared caches.
After that, Android stopped reloading; iPhone was mostly fine already. I’m also migrating away from Web2Native toward a Capacitor setup for more flexibility with these behaviors.
Happy to share my config details if helpful. Thanks again!
David Badilla Salazar Thank you for your guide. Since I’m using WordPress along with the community app for the entire site, it would be great if there were a permanent solution for this. I hope you can address this in a future update. Thanks again!
Hi David Badilla Salazar can you tell me when you are going to use Capacitor?