# Best Prompts for a Subscription Fitness App: ShipNative

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-06-04. 5 min read.
> Source: https://vp0.com/blogs/best-prompts-for-building-a-subscription-fitness-app-with-shipnative

ShipNative is a React Native boilerplate with auth and payments wired in, so prompt the fitness content and paywall logic, not the scaffolding.

**TL;DR.** The best prompts for a subscription fitness app with ShipNative extend the boilerplate instead of rebuilding it: first map where auth and subscription state live, then add a workout content model and Browse screen, a workout player, a paywall gate that reuses the existing subscription check, and onboarding plus progress. ShipNative is a paid React Native and Expo boilerplate (around $99) with payments and auth done. Point your AI editor at a free VP0 design so the design side adds $0.

The best prompts for building a subscription fitness app with [ShipNative](https://www.shipnative.app/) are different from a blank-slate builder, because ShipNative is a React Native and [Expo](https://expo.dev/) boilerplate that already ships auth and payments wired in. The plumbing most apps spend a month on, sign-in and subscriptions, is done, so your prompts (run in an AI editor like Cursor on top of the boilerplate) should focus on the fitness content and the paywall logic, not the scaffolding. Below is the build order. To make the workout screens look right, point your AI editor at a free [VP0](https://vp0.com) design (the free iOS and React Native design library AI builders read from) and tell it to match the layout.

## How ShipNative changes the workflow

With a from-scratch builder you prompt the whole stack. With ShipNative you start from a working app that has authentication and a payments path (commonly Stripe or RevenueCat) already in place, so you extend rather than build foundations. That means prompting against an existing codebase: name the files, follow the existing patterns, and gate features by subscription status. The general prompting method still applies, see [how to prompt an AI app builder](/blogs/how-to-prompt-an-ai-app-builder/).

## The prompt sequence

### 1. Map the boilerplate first

```
Read this ShipNative project and summarize where auth, the subscription
state, and navigation live. I want to add fitness features without breaking
the existing payment flow.
```

### 2. The workout content model

```
Add a content model for programs, workouts, and exercises. Build a Browse
screen listing programs with cover, level, and a Pro badge on premium ones.
Match this layout: [VP0 design description].
```

### 3. The workout player

```
Add a workout player: exercise list, set and rep tracking, a rest timer, and
a Complete action that logs the session. Follow the project's existing
component and styling patterns.
```

### 4. Gate premium content by subscription

```
Gate premium programs behind the existing subscription check: if the user is
not subscribed, show the paywall instead of the player. Reuse the project's
subscription state, do not add a new payments system.
```

### 5. Onboarding and progress

```
Add a short goal-setting onboarding and a Progress screen with streak,
sessions this week, and total minutes. Persist locally and per user.
```

The single rule that matters here: do not reinvent payments. ShipNative already integrates a subscription provider, so reuse it. If you use [RevenueCat](https://www.revenuecat.com/), entitlements are the clean way to gate content. And because subscriptions run through the App Store, follow [Apple's auto-renewable subscription guidelines](https://developer.apple.com/app-store/subscriptions/) so review does not reject the paywall. ShipNative is priced around $99 as a one-time boilerplate, which buys you the payment and auth setup that usually eats the first weeks; you own and can edit the [exported code](/blogs/shipnative-ai-export-github-repository/).

## What each prompt should produce

| Prompt stage | Output | The part to verify |
|---|---|---|
| Map boilerplate | Where auth/subs live | Nothing breaks the payment flow |
| Content model | Programs + Browse | Pro badge on premium |
| Player | Workout flow | Session logs correctly |
| Paywall gate | Subscription check | Premium blocked when not subscribed |
| Onboarding + progress | Goals + stats | Persists per user |

If the gate leaks premium content, fix it precisely: "free users can open Pro programs, route them to the existing paywall when the subscription check is false." That reuses the boilerplate instead of forking it. To confirm the code is yours to edit, [does ShipNative make raw code editable](/blogs/does-shipnative-make-raw-code-editable/) answers it, and for the subscribe UI itself, [the subscription management screen UI](/blogs/subscription-management-screen-ui-ios/) is a reference.

## Make it good, not generic

Fitness apps live or die on the workout experience. Point your AI editor at a VP0 workout and player design so the screens feel right, and the design layer is free, so your spend stays at the $99 boilerplate plus $0 of design cost. For another full prompt walkthrough in this series, see [the best prompts for an AI chat app in Firebase Studio](/blogs/best-prompts-for-building-a-ai-chat-app-with-firebase-with-firebase-studio/).

## Key takeaways

- ShipNative ships auth and payments, so prompt the fitness content, not the foundations.
- Start by mapping where auth and subscription state live before adding features.
- Gate premium content with the existing subscription check; never add a second payments system.
- Follow Apple's subscription guidelines so the paywall passes App Store review.
- Point your AI editor at a free VP0 design so spend stays at the $99 boilerplate plus $0 design.

## Frequently asked questions

### What are the best prompts for building a subscription fitness app with ShipNative?

The best prompts extend the boilerplate: first map where auth and subscriptions live, then add a workout content model and Browse screen, a workout player, a paywall gate that reuses the existing subscription check, and onboarding plus progress. Point your AI editor at a free VP0 design, the free iOS and React Native design library for AI builders, so the screens look right at $0 of design cost.

### Does ShipNative already include payments and auth?

Yes. ShipNative is a React Native and Expo boilerplate that ships authentication and a subscription payments path already wired, so you extend it with features rather than building the foundations. That is the main reason it saves the first weeks of work.

### How do I gate premium content in a ShipNative fitness app?

Reuse the project's existing subscription check: if the user is not subscribed, show the paywall instead of the premium content, and never add a separate payments system. With RevenueCat, entitlements are the cleanest way to express which programs are Pro.

### Will a ShipNative subscription app pass App Store review?

It can, if the paywall follows Apple's auto-renewable subscription guidelines: clear pricing, terms, and restore-purchases. Because ShipNative wires a compliant provider, your job is to present the paywall correctly, not to build billing from scratch.

### Is ShipNative free for building a fitness app?

ShipNative is a paid boilerplate priced around $99 one-time, which covers the auth and payments setup. The VP0 design layer is free, so the design side adds $0 on top of the boilerplate cost.

## Frequently asked questions

### What are the best prompts for building a subscription fitness app with ShipNative?

The best prompts extend the boilerplate: first map where auth and subscriptions live, then add a workout content model and Browse screen, a workout player, a paywall gate that reuses the existing subscription check, and onboarding plus progress. Point your AI editor at a free VP0 design, the free iOS and React Native design library for AI builders, so the screens look right at $0 of design cost.

### Does ShipNative already include payments and auth?

Yes. ShipNative is a React Native and Expo boilerplate that ships authentication and a subscription payments path already wired, so you extend it with features rather than building the foundations. That is the main reason it saves the first weeks of work.

### How do I gate premium content in a ShipNative fitness app?

Reuse the project's existing subscription check: if the user is not subscribed, show the paywall instead of the premium content, and never add a separate payments system. With RevenueCat, entitlements are the cleanest way to express which programs are Pro.

### Will a ShipNative subscription app pass App Store review?

It can, if the paywall follows Apple's auto-renewable subscription guidelines: clear pricing, terms, and restore-purchases. Because ShipNative wires a compliant provider, your job is to present the paywall correctly, not to build billing from scratch.

### Is ShipNative free for building a fitness app?

ShipNative is a paid boilerplate priced around $99 one-time, which covers the auth and payments setup. The VP0 design layer is free, so the design side adds $0 on top of the boilerplate cost.

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*