
Today / Readiness
A daily training view with readiness context and a visible rationale.
iOS strength training
OneMore is a native iOS app from 4WARD Labs LLC. It reads current training context and Apple Health signals, then organizes the next workout decision while keeping the lifter in control.
Pre-beta. Local-first core. Building toward TestFlight.
Real Build Proof
Every screen below was captured on a physical iPhone running the current OneMore build. No renders. No design comps. This is where the product is today.

Today surfaces the current training decision with readiness context and a visible path into the signals behind it.

The Sources view makes the visible signal inputs inspectable, including permissioned Apple Health reads and local training context where available.

The Active Session surface keeps the workout focused on the current lift, current set, rest timing, and the next logged action.
The build is in active development as a native iOS app, with a local SwiftData store. Building toward beta on TestFlight.
Join the waitlist ↗How OneMore Decides
OneMore organizes training context through a simple loop: observe the signals, interpret what changed, recommend the next training move, then reflect the completed work back into the local history.
Continuous Decision Loop
The person decides.
OneMore is being built to organize context and explain tradeoffs without replacing human judgment.
Current App Surfaces
OneMore is pre-beta, but the current iOS build already exposes the core training surfaces needed to inspect signals, prepare a routine, log a session, review history, and manage settings.

A daily training view with readiness context and a visible rationale.

An inspectable signal list for the inputs behind the current decision.

Saved strength routines and lift templates for session setup.

Focused workout logging for the selected routine and current set.

Past training context that helps the app keep recent work visible.

Controls for app preferences, permissions, and local data handling.
Local-First By Design
OneMore’s current core is local-first. The app is being built so training data, Apple Health permissions, export, and local deletion are visible as product controls, not just policy language.
You see what's stored.
Every workout, session, and signal OneMore holds is inspectable in-product. Settings keeps data controls discoverable in the current build.
You control what's shared.
Apple Health permissions are granular and reversible. Reads and optional completed-workout writeback are user-controlled.
You can export or delete, anytime.
Export your full history as JSON to the Files app on your phone. Delete everything in one tap and wipe the local store irreversibly. Your data belongs to you, not to the app.
Today · In the build
Current build boundary
No cross-device account layer is described here. The site should only claim the local-first behavior and in-product controls that are visible in the current build.

Settings · Inspectable
OneMore keeps permission and data controls inside the app. This page uses the current Settings Hub screenshot until the latest dedicated Data & Privacy screenshot is ready for the site.
When completed-workout writeback is enabled, OneMore writes only workout start time, end time, and unique workout/session identifiers to Apple Health.
Apple Health permissions
Building decision technology means holding a discipline: the user can see, control, export, and delete local app data.
Read the privacy policy ↗Building Toward Beta
OneMore is being prepared for TestFlight with native SwiftUI, SwiftData, Apple Health reads, workout logging, routines, history, settings, and visible Data & Privacy controls. 4WARD Labs LLC is the company behind the product.
Join the Beta
OneMore is pre-beta. Join the invite list if you want to train with the current iOS build and share practical feedback.
Small cohorts. iOS only. Real product feedback.