Forem: RunnerY

Run or Pay? ~App Store Review Submitted!!~

RunnerY — Mon, 16 Feb 2026 12:03:20 +0000

Pay if you don’t run??

I built an app to help people overcome lack of exercise!

Choose how much you’ll pay if you don’t run for 30 minutes within 6 days
Select your commitment amount (¥500–¥10,000)
Track your running distance and time using the in-app timer
If you fail to complete the challenge in time, the selected amount is charged
If you succeed, the payment is canceled

In other words, this app creates a financial commitment to yourself, forcing you into a situation where you have to run.

Daily Report — 2026/02/16

🎉 App Store submission completed!

Submission date: Feb 16, 2026
Current status: In review (usually 1–3 days)
TestFlight: External testing ongoing
Stripe: Switched to production mode

Progress Summary (since Feb 1)

Over the past two weeks, I moved from the final stage of MVP development to App Store submission.

✅ Major Achievements

1. Onboarding implementation (early February)

Added 5 onboarding screens
Pre-challenge explanations (measurement method, reducing psychological friction)
Clear explanation of “What happens if you pay?”
Added image assets (English & Japanese)

2. Built-in GPS workout tracking (mid-February)

Implemented in-app running tracking
Integrated CoreLocation + HealthKit
Real-time display: elapsed time, distance, pace
Automatically saves data to HealthKit after tracking
Simple experience without external apps

3. Challenge parameter update

Goal time: 60 minutes → 30 minutes
Easier for beginners to complete
Achievable with 15 minutes × 2 runs
Challenge period remains 6 days

4. Stripe production migration (Feb 15)

Switched from test mode to production mode
Production API keys configured
Edge Functions updated
iOS publishableKey updated

Stack

iOS: SwiftUI + HealthKit + CoreLocation
Auth: Sign in with Apple
Backend: Supabase (Auth, PostgreSQL, Edge Functions)
Payments: Stripe (PaymentIntent with manual capture)
Monthly cost: ¥0 (excluding Apple Developer Program)

Current Feature Set (v1.0)

Core Features

Sign in with Apple authentication
30-minute running challenge in 6 days (fixed)
Commitment amount selection (¥500–¥10,000)
Built-in GPS workout tracker
HealthKit integration (Apple Watch & other apps supported)
Stripe pre-authorization (no charge if successful)
Automatic charge on failure
Early completion support
Challenge history view
Onboarding experience

Not included in v1.0 (future work)

Notifications / reminders
Custom challenge duration
Custom goal time
Apple Watch standalone app
Social features
Multi-language support (English only for now)

Roadmap

v1.1 — Improvements (after approval)

UI/UX improvements based on feedback
Bug fixes and crash fixes
Performance optimization
Notifications (reminders)
Onboarding improvements

v1.2 — Feature expansion

Detailed challenge history
Stats & graphs
Apple Watch support
Widgets

v2.0 — Major update

Customizable goal time

Reflections & Learnings

Changes over the past two weeks

On Feb 1, I had just started external TestFlight testing.

In two weeks, I completed:

Onboarding (major UX improvement)
Built-in tracking feature
Production environment migration
App Store submission

Decisions

Why reduce the goal?

To improve first-time user retention.

60 minutes felt like too high of a psychological barrier.

Why add built-in tracking?

External app setup was too complex for beginners.

I prioritized simplicity.

Summary

The Run or Pay MVP has finally reached App Store review.

Two weeks ago, external testing had just begun.

Since then, onboarding, built-in tracking, and production migration were completed — culminating in submission.

While waiting for review results, I’ll focus on marketing preparation and TestFlight feedback.

Next update when the review result arrives!

A “Pay If You Don’t Run” App? Onboarding and Marketing should be serious

RunnerY — Sat, 31 Jan 2026 16:23:55 +0000

What I’m Building

Users set how much money they’re willing to pay if they fail to run 60 minutes within 6 days, and the app pre-authorizes that payment.
Running activity is tracked via HealthKit using an iPhone or Apple Watch.
Because users are financially committed, they’re effectively forced to run—helping improve running habits in Japan.
If the user fails to reach the goal, the pre-committed money is transferred to the operator. If the goal is achieved, the payment authorization is canceled.

If you’re interested in trying it out, please leave a comment. I’ll share a test version of the app somehow!

Daily Report - 2026/02/01

Status

TestFlight: ✅ External testing live
Testers: Friends have started testing
Phase: Onboarding & technical validation

Progress Since 2026/01/29

✅ Challenge Period Change

Shortened from 7 days → 6 days
Reason: To avoid expiration risk of Stripe authorization (7-day limit)
Secured a 1-day safety margin

✅ UI/UX Improvements

Improved loading state handling (ChallengeView)
Improved remaining time display
Added clearer challenge description (“Run 60 minutes in 6 days”)

✅ Stronger Authentication Validation

Blocked authorization and challenge actions when not logged in
Added authentication checks to the complete-challenge Edge Function

✅ `complete-challenge` Edge Function

Purpose: Called from the UI when the goal is achieved before the deadline
Separate from process-expired-challenges (automatic expiration handling)
Cancels the authorization and completes the challenge immediately

✅ External Testing Started

Passed Apple review
Began distribution via public link to friends

Today’s Focus

🔶 Measurement Onboarding Validation

Verify whether users can correctly record running activity
Identify issues caused by insufficient explanations
Consider a YouTube video or in-app tutorial

🔶 Technical Validation

Run E2E tests personally (create challenge → achieve → complete)
Verify early-completion flow via complete-challenge
Prepare tests for automatic judgment after 6 days

Next Steps

This Week

[ ] Add a “How to Measure” link to ChallengeView
[ ] Create a YouTube video explaining how to record running activity
[ ] Collect feedback from friends

Before Production Release

[ ] Finalize onboarding
[ ] Switch Stripe to live mode
[ ] Submit for App Store review

Notes

Instructions for Testers

Record Running using the Workout app on Apple Watch or iPhone
Nike Run Club / Strava must have Health app integration enabled

Observation Points

Can first-time users understand how to measure running?
Are there any issues in the HealthKit permission flow?
Is running activity reflected correctly in the app?

Run or Pay? App building. Done Apple Developer Program & inside TestFlight

RunnerY — Wed, 28 Jan 2026 15:44:45 +0000

What I’m Building

Users set an amount of money they agree to pay if they fail to run at least 60 minutes within a week, and authorize the payment in advance.
Running time is measured via HealthKit using an iPhone or Apple Watch.
Because money is on the line, users are effectively forced to run, helping build consistent exercise habits.
If the user fails to reach the target, the pre-authorized payment is captured by the service. If the target is achieved, the payment is automatically canceled.

If you try the beta version, I'll send you TestFlight invitation code! Please comment!

The app icon is ready:

What I’ve Done So Far

Finally completed account registration
Implemented Sign in with Apple
Since the app was designed around Apple ID login from the start, I can now test all features properly on a real device
Added logic to measure running time via HealthKit

Concern #1: Payments in Production

Payments are the most anxiety-inducing part when thinking about real-world usage.
So far, I’ve been doing a lot of vibe coding, but payment-related logic needs proper test coverage.
Main concerns:
- Whether the cron job that checks user status and determines challenge completion works reliably
- Whether payment cancellations are handled correctly
I’m also unsure whether Japanese users will feel comfortable making payments via Stripe, which isn’t very familiar in Japan.

Concern #2: Measurement via External Apps

The app relies on workouts recorded by external apps, so all of the following need to work correctly:

Apple Watch workouts
iPhone Fitness app workouts (latest iOS)
Nike Training / Nike Run Club workouts
Strava workouts

All of these need to be tested — ideally by real users.

For the MVP, I decided to skip in-app workout tracking, since the implementation and running costs don’t justify it at this stage.

Status

Apple Developer Program: ✅ Approved
TestFlight: ✅ Internal testing successfully distributed
App State: Ready for TestFlight distribution

Progress Since 2025-01-25

✅ Sign in with Apple

Enabled Sign in with Apple in Xcode Capabilities
Integrated with Supabase Auth
Successfully tested on a real device

✅ Shortened Challenge Duration

Reduced from 28 days → 7 days
Easier to test and lowers user drop-off risk

✅ HealthKit Background Delivery

Implemented automatic DB sync when a workout ends
Progress updates even when the app is killed
Uses enableBackgroundDelivery in HealthKitBackgroundService.swift
Users don’t need to open the app for progress to be reflected

✅ TestFlight Distribution

Xcode Cloud setup completed
Build successfully uploaded to App Store Connect
Created internal test group “friend”
Build 1.0 (7) is available for testing

✅ App Store Connect Setup

Added NSCameraUsageDescription (required by Stripe SDK)
Export compliance completed (no encryption)
Test information fully filled in

Next Steps

[ ] Test the TestFlight build on my own iPhone
[ ] Apply for external testing (Apple review)
[ ] Distribute via public TestFlight link to friends

“Pay-if-you-don’t-run” app by vibe coding ~ Still waiting on Apple Developer Program approval 😤

RunnerY — Sun, 25 Jan 2026 05:52:16 +0000

What I'm Building

I’m building an app with the following concept:

Users are asked how much money they want to put at stake for the month, and a payment authorization is set up in advance.
Running distance is tracked via HealthKit using an iPhone or Apple Watch.
Because money is on the line, users are effectively forced to run.
This (hopefully) contributes to improving exercise habits in Japan.
If the user fails to reach their self-defined distance goal, the pre-committed money is paid to the operator.

This is based on the concept of commitment in psychology and economics.

A similar app exists overseas called Stickk.

What Went Well

HealthKit integration probably works. Let me test it already.
The app icon is done.

There isn’t much I can do right now.

Maybe create a public Notion page, or think about marketing strategies.

I haven’t written any tests.

Right — I should write tests.

Status

Apple Developer Program: Registered on 1/23, not yet activated
App status: MVP is basically complete, waiting for Sign in with Apple

Completed Features

✅ Stripe Payments

PaymentSheet integration completed
Authorization-only flow using capture_method=manual
Successful testing on a real device
Fixed PaymentSheet presentation error (handled topmost ViewController)

✅ HealthKit Integration

Implemented running data retrieval
Added NSHealthShareUsageDescription to Info.plist
Successfully authorized and fetched data on a real device

✅ Batch Processing (Edge Functions)

process-expired-challenges: evaluates 28-day challenges and handles payments
update-progress: updates user progress
Deployed to Supabase

✅ GitHub Actions

.github/workflows/process-challenges.yml
Runs automatically every day at 00:00 UTC
Secrets configured (SUPABASE_ANON_KEY)

✅ UI Improvements

Countdown display for remaining days/hours
Fixed deposit amount display
Changed challenge duration from monthly to 28 days

✅ App Store Preparation

Privacy policy created (docs/privacy-policy.md)
App Store description written (docs/appstore-description.md)
App icon set (1024x1024)

Pending Tasks

⏳ Sign in with Apple

Blocker: Waiting for Apple Developer Program approval
Tasks after approval:
1. Enable Sign in with Apple in Xcode Capabilities
2. Implement Supabase Auth integration
3. Update RLS policies

⏳ Database Persistence Testing

Currently blocked by RLS (writes not allowed without authentication)
Temporarily testing with a dev user ID

⏳ TestFlight Distribution

To be done after Developer Program approval

⏳ App Store Submission

To be submitted after all features are implemented and tested

Tech Stack

Category	Technology
iOS	iOS 17+, SwiftUI
Auth	Sign in with Apple (planned)
Database	Supabase
Payments	Stripe
Activity Data	HealthKit
Batch Jobs	Supabase Edge Functions
CI/CD	GitHub Actions

Key File Changes

1/23

StripeAuthorizer.swift – Stripe PaymentSheet integration
Challenge.swift – Added stripePaymentIntentId, remaining time calculation
ChallengeView.swift – Added countdown UI
SupabaseChallengeStore.swift – Dev user ID support
Info.plist – Added HealthKit configuration
Created and deployed Edge Functions
Configured GitHub Actions

1/24

StripeAuthorizer.swift – Fixed PaymentSheet presentation issue
- Updated to retrieve the topmost ViewController

Next Actions

Wait for Developer Program approval (up to 48 hours)
After approval:
- Implement Sign in with Apple
- Integrate Supabase Auth
- Configure RLS policies
- Distribute via TestFlight
- Submit to the App Store

Notes

Apple Developer Program: $99/year (registered on 1/23)

An app where you get charged if you don’t run: applying to the Apple Developer Program and connecting Supabase and Stripe

RunnerY — Fri, 23 Jan 2026 13:30:30 +0000

Here’s the rough idea.

Ask users how much money they’re willing to put at stake for the month, and reserve (authorize) that amount in advance.
Track the user’s running distance via HealthKit using an iPhone or Apple Watch.
Because money is on the line, users are effectively forced to run, which (hopefully) contributes to improving exercise habits in Japan.
If the user fails to reach the distance they originally set, the pre-committed money is paid out to the operator.

By the way, this is my second time doing solo development, and I’m basically a vibe coder!

I occasionally write code, but my day job is closer to being a data analyst (mostly sales, though).

Today’s Summary

The Apple Developer Program apparently takes up to two days to reflect changes, which is slower than expected.
Because authentication isn’t working yet, I can’t make much progress on testing.
Still, things moved along nicely overall. I’d like to have friends test it this weekend, but realistically I might not make it in time.

2026-01-23 Development Log

What I Did

1. Apple Developer Program Registration

Paid the $99 fee
Waiting for it to reflect in Xcode (up to 48 hours)
Sign in with Apple will be implemented after that

2. End-of-Month Batch Processing (Edge Functions)

Created and deployed process-expired-challenges
- Determines challenges that have passed 28 days
- Goal achieved → cancel authorization (refund)
- Goal not achieved → capture payment (charge)
Created and deployed update-progress
- Updates progress (running minutes)

3. GitHub Actions Setup

Created .github/workflows/process-challenges.yml
Runs process-expired-challenges every day at 00:00 UTC
Secrets will be configured after pushing to GitHub

4. HealthKit Integration

Added NSHealthShareUsageDescription to Info.plist
Added requestAuthorization() to the ActivityMinuteSource protocol
Request HealthKit authorization on app launch in ChallengeView
Real device testing successful 🎉
- HealthKit authorization dialog appeared
- Successfully obtained permission to read workout data

5. UI Improvements

Added remaining time display
- 2+ days: “X days remaining”
- 1–2 days: “1 day and X hours remaining”
- Less than 1 day: “hh:mm remaining”
Fixed commitment amount display
- Adjusted timing for closing the sheet after payment completion

6. Code Changes

Added stripePaymentIntentId to the Challenge model
Added remaining time calculation properties to the Challenge model
Updated SupabaseChallengeStore to use a development user ID

Blockers

Waiting for Developer Program Activation

Sign in with Apple cannot be used yet
Because authentication is required by RLS, database save testing cannot be done

Temporary Workaround (Not Implemented)

Relaxing Supabase RLS would allow testing without authentication

Next Steps

Confirm Developer Program Activation
- Check via Xcode → Settings → Accounts
- If the Team appears, it’s good to go
Implement Sign in with Apple
- Integrate with Supabase Auth
- Create Supabase users from Apple IDs
Test Database Persistence
- Create a challenge → verify it’s saved in Supabase
Prepare for Release
- Push to GitHub & configure Secrets
- Create app icon
- Create privacy policy

Commit History

feat: add countdown UI and commitment money
Plus Edge Functions deployments and other changes

Verified Functionality

Feature	Simulator	Real Device
Stripe Payment	✅	✅
HealthKit Auth	-	✅
UI Rendering	✅	✅
DB Persistence	❌ RLS	❌ RLS

I'm going to build an app where you lose money if you don’t run.

RunnerY — Thu, 22 Jan 2026 17:31:04 +0000

What I Did Today

What I did

Came up with the idea
Threw the idea to GPT and some friends
Roughly designed the architecture and had it built up to this point
Generated an app icon to get myself hyped

There’s no strong guarantee this will work, but I want to try getting an iOS app through App Review—and honestly, I want to run more myself—so I’m building this.

The Idea

Users sign up
They are asked how much money they’re willing to put at stake for the month
Running distance is tracked via HealthKit
Because money is on the line, users are forced to run
This (hopefully) contributes to improving exercise habits in Japan
If the user fails to reach their self-set goal, their money is charged

Context

This is my second time doing solo development, and I’m basically a vibe coder.

I occasionally write code, but my day job is closer to a data analyst (mostly sales, though).

Spec

If you don’t run this month,

how much money are you okay with losing?

※ No charge will occur if you achieve your goal.

[ ¥500 ] [ ¥1,000 ] [ ¥3,000 ]
↑ Recommended
[ Custom input ]

Rules

Minimum: ¥500
Default: ¥1,000
Maximum: ¥10,000

2026/01/23 — Work Log

✅ Completed Tasks

1. Created iOS project skeleton

Built a directory structure based on DDD architecture:

ios/RunForPay/
├── App/
│   ├── RunForPayApp.swift      # App entry point
│   ├── AppContainer.swift      # DI container
│   └── ContentView.swift       # Root view
├── UI/
│   ├── LoginView.swift         # Sign in with Apple
│   ├── ChallengeView.swift     # Progress display
│   ├── DepositSelectView.swift # Deposit selection
│   └── ChallengeViewModel.swift
├── Domain/
│   ├── Challenge.swift         # Entity
│   ├── Minutes.swift           # Value Object
│   ├── DepositAmount.swift     # Value Object
│   └── Ports.swift             # Protocols
├── UseCases/
│   ├── GetMonthlyRunningMinutes.swift
│   └── AuthorizeDeposit.swift
├── Infra/
│   ├── Measurement/
│   │   └── HealthKitMinuteSource.swift
│   ├── Payments/
│   │   └── StripeAuthorizer.swift
│   └── Persistence/
│       └── InMemoryChallengeStore.swift
└── Shared/
    └── DateUtils.swift

Xcode project setup Created RunForPay.xcodeproj

Configured HealthKit permission messages in Info.plist

Set HealthKit / Sign in with Apple entitlements in RunForPay.entitlements

Skeleton implementation (16 files) Domain

Challenge, Minutes, DepositAmount, Ports

UseCases

GetMonthlyRunningMinutes, AuthorizeDeposit

LoginView, ChallengeView, DepositSelectView, ChallengeViewModel

Infra

HealthKitMinuteSource, StripeAuthorizer, InMemoryChallengeStore

Shared

DateUtils

🚧 Blockers
Cannot install Xcode: macOS 15.6 or later is required

Need to update macOS

▶️ Next Steps
Update macOS

Install Xcode

Open project in Xcode and set Team ID

Add Stripe SDK / Supabase SDK via Swift Package Manager

Confirm build

Forem: RunnerY

Run or Pay? ~App Store Review Submitted!!~

Daily Report — 2026/02/16

🎉 App Store submission completed!

Progress Summary (since Feb 1)

✅ Major Achievements

1. Onboarding implementation (early February)

2. Built-in GPS workout tracking (mid-February)

3. Challenge parameter update

4. Stripe production migration (Feb 15)

Stack

Current Feature Set (v1.0)

Core Features

Not included in v1.0 (future work)

Roadmap

v1.1 — Improvements (after approval)

v1.2 — Feature expansion

v2.0 — Major update

Reflections & Learnings

Changes over the past two weeks

Decisions

Summary

A “Pay If You Don’t Run” App? Onboarding and Marketing should be serious

What I’m Building

Daily Report - 2026/02/01

Status

Progress Since 2026/01/29

✅ Challenge Period Change

✅ UI/UX Improvements

✅ Stronger Authentication Validation

✅ complete-challenge Edge Function

✅ External Testing Started

Today’s Focus

🔶 Measurement Onboarding Validation

🔶 Technical Validation

Next Steps

This Week

Before Production Release

Notes

Instructions for Testers

Observation Points

Run or Pay? App building. Done Apple Developer Program & inside TestFlight

What I’m Building

What I’ve Done So Far

Concern #1: Payments in Production

Concern #2: Measurement via External Apps

Status

Progress Since 2025-01-25

✅ Sign in with Apple

✅ Shortened Challenge Duration

✅ HealthKit Background Delivery

✅ TestFlight Distribution

✅ App Store Connect Setup

Next Steps

“Pay-if-you-don’t-run” app by vibe coding ~ Still waiting on Apple Developer Program approval 😤

What I'm Building

What Went Well

Status

Completed Features

✅ Stripe Payments

✅ HealthKit Integration

✅ Batch Processing (Edge Functions)

✅ GitHub Actions

✅ UI Improvements

✅ App Store Preparation

Pending Tasks

⏳ Sign in with Apple

⏳ Database Persistence Testing

⏳ TestFlight Distribution

⏳ App Store Submission

Tech Stack

Key File Changes

1/23

1/24

Next Actions

Notes

An app where you get charged if you don’t run: applying to the Apple Developer Program and connecting Supabase and Stripe

Today’s Summary

2026-01-23 Development Log

What I Did

✅ `complete-challenge` Edge Function