CASE STUDY · OWN PRODUCT
Zoku Athletics: how we build our own app and its website
This is a translation provided for convenience. The Spanish version is the legally binding text and prevails in case of any discrepancy. Read the Spanish version.
Zoku Athletics is BAZROX’s own product: a training app for hybrid athletes, with a bilingual website that is already live and an Android app in closed testing. It is the only project we can name, so we tell the whole of it, including what is not there yet.
Context
Zoku Athletics is an app for people who combine strength, functional training and outdoor sessions. It is built by BAZROX, a separate software studio under the same ownership: the relationship is creator and product, not supplier and client.
The website lives at zokuathletics.com, in Spanish with an English version, and it is where accounts are created and where plans will be sold once they are switched on. The app does not sell subscriptions.
- The product’s website
- zokuathletics.com (opens in a new tab)
- What Zoku Athletics is
- The product’s own introduction, on its website (opens in a new tab)
What has been built
Only what can be checked by opening the website or reading what it publishes itself. None of what follows carries figures, because we have not verified any.
- Bilingual website
- Built with Next.js, in Spanish and English with alternate links between languages. With a guides section, user accounts (sign-up, sign-in, recovery and deletion) and subscription plans.
- Android app
- In closed testing, not in the stores. The iOS version is in preparation and has no date.
- WOD timer
- A workout timer with a training load that adapts to the fatigue the user reports.
- Routes with contact alerts
- GPS tracking of the session: if the user stays still, the app asks whether they are okay and, if there is no answer, opens the messaging app with their location for their contacts. It is a notification aid, not an emergency service.
- Camera-based form feedback
- Pointers on technique for squats, lunges, deadlifts, presses, dips and pull-ups. It is information, not a diagnosis.
- Benchmark community
- Reference workouts from the Zoku catalogue with a global ranking between users.
The same decisions as with a client
Building our own product makes us take the decisions we later stand behind in front of a client. Three of them repeat in every project.
- Scope in writing before building
- Every phase of Zoku has a list of what is in and what is out. It is what stops the product growing by accumulation, and it is what we ask of any client before estimating.
- The code belongs to whoever pays for it
- Zoku is ours, and so are its code and its documentation. With a client the rule is the same: the code we develop specifically for their project is theirs, with its repository and its documentation, once the corresponding amounts have been paid.
- Maintenance from day one
- The website is live and maintained; the app is tested before it is opened to everyone. Launching and then sustaining is the same order we follow with a client’s system.
Actual status
The website is live and in use. The Android app is in closed testing and has no launch date; the iOS one is in preparation, also without a date. Paid plans exist on the website but are not being charged yet.
We publish no figures for users, downloads or results, because we have not verified them and because this case exists to show how we work, not to sell the product.
Where to go next
Let’s start with what you have today.
If what you need is a system for your process or a website built like software, these are the pages that explain it.
- Web development
- A website you won’t have to rebuild every two years
- No commitment.
- Reply in under 24 working hours.
- Scope, deliverable and price in writing before we start.