IEQ MVA

The context

The Foursquare Church of Jardim Vista Alegre needed two things that rarely come together: a digital presence for the community (services, announcements, Bible, music) and an internal management tool (members, visitors, contributions, work schedules, Sunday school). Instead of an off-the-shelf app, I built it as the flagship of igreja.studio — my own white-label platform, designed so the same product can serve other churches under their own brand.

Decisions that were mine

1. 01Figma before a single line of code

   I designed the whole product first — a dark, sober identity, module-based navigation, clear hierarchy between the public side (Bible, services, music) and the administrative side. Validating a flow with the pastor on a Figma screen costs minutes; in a shipped app, it costs weeks.

2. 02Expo, to iterate at the speed of a community

   A church changes its schedule every week. I chose Expo + React Native for over-the-air updates and a short release cycle — a request from Sunday service can be live before the next Sunday.

3. 03A white-label, not a one-off

   I applied the lesson from years on a banking white-label to my own product: IEQ MVA runs on igreja.studio, where members, schedules, contributions and notifications are isolated NestJS modules on Azure, and each church is a tenant with its own brand. The next church onboards by configuration, not by rewrite.

4. 04From requirements to answering Apple review

   I ran the full publishing cycle: developer accounts, store assets, privacy policy, review. It is the kind of ownership you only learn by doing — and doing alone.

Where it landed

Live on the App Store and Google Play, in continuous use by the community — multi-version Bible, work schedules, Sunday school, contributions via Pix — and a platform ready to onboard more churches under their own brands.