From community platform to web + mobile product.
Bethel Lakewood — events, giving, and membership on one system.
Problem
A church community needed to run events, donations and member participation on web and mobile.
Constraints
Web plus native iOS and Android. Stripe for donations. Member profiles and events.
System
Next.js web application and React Native iOS/Android apps, with Stripe integrated across surfaces.
Architecture
One membership and events model; payments as a shared Stripe integration rather than a web-only checkout.
Product
Members can participate, follow events, and give on the surface they actually use.
Engineering
Native mobile clients, web app, and multi-surface Stripe.
Outcome
A community product covering events, donations and profiles on web and mobile. We do not invent conversion metrics for this case.
What comes next
The same pattern — one system, several clients, payments as infrastructure — is how we approach other community products.