Release-candidate builds are in testing

We now have release-candidate builds of both the iOS and Android apps, and they are in internal testing.

What a release candidate actually is

A release candidate is the version we believe is ready to ship, being put through its paces to prove it really is. Nothing new gets added at this stage. The job is to try hard to break it before anyone else can.

The whole loop, end to end

We are testing the full journey a real person takes. Search for a topic and browse experts by their per-minute rate. Open a profile with its services, rate and reviews. Book a set number of minutes and pay up front through Stripe, so those minutes are reserved. Then join the video call inside the app at the time you booked, on nothing more than a phone and a steady connection.

The expert side gets the same scrutiny: setting up a profile, adding services and a per-minute rate for each, publishing availability, taking the call, and being paid out automatically through Stripe afterwards.

Native, on purpose

Both apps are built native for iOS and Android rather than wrapped once and shipped twice. It is more work, but a call needs to feel immediate, and that is hard to fake. We are running the builds on real devices and poking at the awkward edges: dropped connections, cancellations, time zones, the things that only show up when you actually use it.

When these builds pass, they are the ones we submit.