Fold installs from the browser today, with no app store. That is deliberate: a church secretary on mobile data should not have to download forty megabytes to record a service.
So the first question is not how to build the app. It is whether one earns its place, and where a native app genuinely beats what the browser already does: offline attendance in a hall with no signal, a camera for member photographs, push notifications that actually arrive.
What you would be doing
- Work out honestly which parts need native and which do not
- Build offline first attendance, if that is what the answer turns out to be
- Keep parity with the web product rather than forking the logic
What we are looking for
- Shipped mobile work, React Native, Flutter or native, we are not precious about it
- An instinct for what a weak connection does to an application
- Willingness to argue that a feature should not be built
- Based in Ghana
What you get
- A genuinely open question to answer, not a spec to implement
- The say on the architecture, if the case is made
- Users you can go and watch, in churches, on Sundays
Interested?
Write to us and say which of these you mean and why. A person reads every message and replies within a day. There is no form with twenty fields, and no closing date.