We're currently evaluating Wappler for a digital membership card platform designed for museums, zoos, aquariums, and visitor attractions. The goal is to create a modern membership experience while keeping the application easy to maintain and scalable.
The platform includes secure member authentication, QR code check-ins, Apple Wallet and Google Wallet digital membership card , loyalty rewards, guest passes, membership renewals, CRM integrations, and push notifications. Since many organizations already use existing ticketing and CRM systems, API integration and performance are important considerations.
One area I'm particularly interested in is how developers structure larger Wappler applications. Do you separate business logic into APIs, or keep most workflows within Server Connect? How do you organize reusable actions, authentication, and database queries as the application grows?
We're building these capabilities as part of the MembershipAnywhere platform, and I'd love to learn from developers who have built production-ready applications with Wappler. Any recommendations for project architecture, deployment, performance optimization, or API best practices would be greatly appreciated.
From the description, everything you describe is well within the scope of Wappler.
The only part I have not personally done is the Apple wallet/ Google wallet part but pretty sure it wont be difficult.
I would recommend you use node.js rather than PHP as this allows for extra functionality like live updates scheduling and much more.
Also there is a large number of custom extensions available to add parts of functionality not in the core of Wappler.
These both come down to their respective providers so you have to configure these within their dashboards first prior to using the Stripe integration in Wappler itself (validation and verification applies). As Brian said not too difficult and are very well documented on the Stripe Developer area. Everything else is a yes. Lots of examples of various member based applications here in the Community. You can find them in the Showcase section.
I've created a number of large systems similar to the one you're developing. Wappler is easily capable of doing that (and more). As @Cheese and @Hyperbytes mention above, there's also scope to use extensions (or create your own) to further increase the capabilities.
Workflows are in Sever Connect and take advantage of APIs to easily organise the structure. Third party APIs can be used for any additional data your project requires.