Skip to content

monetization.md

Latest commit

 

History

History
826 lines (572 loc) · 15.4 KB

monetization.md

File metadata and controls

826 lines (572 loc) · 15.4 KB
Raw

WalkSafe Monetization Strategy

WalkSafe uses a Pay What You Want monetization model.

The app is free to use for everyone. Users can choose to contribute any amount, including €0. There are no ads, no premium safety paywalls, and no selling of location data.

The core principle is:

Safety should be accessible to everyone.

WalkSafe is built as a mission-driven safety app. Monetization should support the product without reducing trust, blocking essential safety features, or making users feel that they need to pay in order to be safe.

Table of Contents

Monetization Philosophy

WalkSafe is a safety product. The monetization model must protect the trust of users.

A traditional premium model could create the wrong feeling:

Pay more to be safer.

WalkSafe should avoid that.

Instead, the model should communicate:

Use WalkSafe for free.
If it helps you, support it with any amount you want.

The app should feel accessible, ethical, and trustworthy.

WalkSafe should never make users feel guilty for choosing €0. The free option must be genuine.

Core Model

WalkSafe uses one monetization model:

Pay What You Want

Users can choose:

€0
€1
€2.99
€5
€10
Custom amount, if supported later

The user can contribute either:

One-time contribution
Monthly contribution

The recommended default contribution is:

€2.99 per month

But the user is always free to choose €0.

What Users Get for Free

All core safety features are free.

WalkSafe does not lock safety behind a paywall.

Free users get:

  • Account creation
  • Friend system
  • Start a safety trip
  • Automatic current location as starting point
  • Destination selection
  • Walking, cycling, and driving modes
  • Planned route display
  • Live location sharing
  • Friends can follow the live route
  • Automatic arrival notification
  • Route deviation detection
  • Delay detection
  • Emergency button
  • Emergency notifications
  • Basic 24-hour location timeline
  • Status updates during a trip
  • Battery low warning
  • Location lost warning
  • Privacy settings
  • Permission management

The goal is simple:

A user who pays €0 should still be able to use WalkSafe as a complete safety app.

What Supporters Get

Supporters do not receive better safety.

Supporters receive recognition and optional non-essential benefits.

Possible supporter benefits:

  • Supporter badge
  • Founder Supporter badge for early contributors
  • Optional name on a supporter wall
  • Early access to experimental features
  • Small app personalization options
  • Thank-you message after contribution
  • Monthly impact update
  • Community voting on future features
  • Access to beta testing groups

Important:

Supporters may get recognition.
Supporters should not get exclusive safety features.

This keeps the model ethical and trust-based.

Suggested Contribution Tiers

The contribution screen should show clear options.

€0
Use WalkSafe for free

€1/month
Supporter

€2.99/month
Recommended contribution

€5/month
Strong supporter

€10/month
Sponsor safety for others

For one-time contributions:

€1
Small support

€5
Helpful support

€10
Strong support

€25
Sponsor safety access

The exact pricing can be adjusted later, but the €0 option should always remain visible and valid.

Why Pay What You Want Fits WalkSafe

Pay What You Want fits WalkSafe because the product is mission-driven.

Users are not buying entertainment or productivity features. They are supporting a safety tool that can help them, their friends, and their community.

This model works especially well when:

  • The app creates emotional value
  • The mission is clear
  • Users trust the product
  • Costs are transparent
  • Contributions feel meaningful
  • The free version is genuinely useful
  • The app avoids manipulative paywalls

WalkSafe should position contributions as support for the mission, not as a forced purchase.

What WalkSafe Will Not Do

WalkSafe should not monetize in ways that damage trust.

WalkSafe will not:

  • Sell location data
  • Sell movement profiles
  • Show third-party ads
  • Lock emergency features behind payment
  • Lock live location behind payment
  • Charge users to send SOS alerts
  • Use dark patterns to force payment
  • Shame users who choose €0
  • Hide the free option
  • Make safety dependent on subscription status

Strong positioning:

No ads.
No selling location data.
No premium safety paywall.
Pay what you want.

In-App Monetization Flow

The monetization flow should be calm, transparent, and optional.

A possible flow:

1. User opens WalkSafe
2. User uses the app for free
3. After a successful trip or after several uses, WalkSafe shows a support message
4. User can choose €0 or any contribution
5. If the user contributes, they become a supporter
6. If the user chooses €0, they continue using WalkSafe normally

The support screen should never interrupt an emergency flow.

Never show monetization prompts:

  • During SOS
  • During active danger alerts
  • While the user is trying to start an urgent trip
  • While the user is dealing with a route deviation warning
  • When location permissions fail
  • When the app detects possible risk

Best Moments to Ask for Support

The best time to ask for support is after WalkSafe has delivered value.

Good moments:

After Safe Arrival

You arrived safely.
WalkSafe is free for everyone.
Want to help keep it that way?

After Several Completed Trips

You have completed 5 WalkSafe trips.
If WalkSafe helps you feel safer, you can support the project with any amount.
€0 is completely okay.

From Settings

Add a permanent menu item:

Support WalkSafe

After a Friend Uses WalkSafe Because of the User

Your safety circle is growing.
Support WalkSafe to help keep it free for everyone.

Monthly Transparency Update

This month, supporters helped cover 68% of WalkSafe server costs.
Thank you for keeping WalkSafe accessible.

Messaging and Copy

WalkSafe should use honest, mission-based copy.

Main Support Screen

WalkSafe is free because safety should be accessible to everyone.

If WalkSafe helps you or someone you care about, choose any amount to support the project.

€0 is completely okay.

Short Version

Pay what you want.
Use WalkSafe for free.
Support us only if you can.

Strong Brand Message

Safety should not be a subscription.

Alternative Brand Message

Everyone deserves to get home safely.

Contribution Confirmation

Thank you for supporting WalkSafe.

Your contribution helps keep the app free for people who cannot pay.

€0 Confirmation

No problem.
WalkSafe is still fully available to you.
Stay safe.

This message is important. It reinforces that €0 is valid.

Technical Implementation

WalkSafe should not implement a premium entitlement system.

Instead, it should implement a supporter system.

There should be no feature checks like:

if (user.isPremium) {
  unlockSafetyFeature();
}

Instead:

if (user.isSupporter) {
  showSupporterBadge();
}

Safety features should not depend on payment state.

Data Model

Example supporter status model:

export type SupporterStatus = {
  uid: string;

  contributionStatus: "none" | "active" | "cancelled" | "expired";

  contributionType?: "one_time" | "monthly";

  amountCents?: number;
  currency?: "EUR" | "USD" | "GBP";

  supporterSince?: string;
  lastContributionAt?: string;

  isFounderSupporter?: boolean;
  showOnSupporterWall?: boolean;

  paymentProvider?: "apple" | "google" | "stripe" | "revenuecat";

  createdAt: string;
  updatedAt: string;
};

Example Firestore structure:

users/{uid}
  displayName
  photoUrl
  supporterStatus
  createdAt
  updatedAt

supporters/{uid}
  contributionStatus
  contributionType
  amountCents
  currency
  supporterSince
  isFounderSupporter
  showOnSupporterWall
  paymentProvider

contributions/{contributionId}
  uid
  type
  amountCents
  currency
  provider
  providerTransactionId
  createdAt

Supporter status should be used only for recognition, not safety access.

App Store and Play Store Implementation

For mobile apps, contributions should be implemented carefully using platform-compliant payment systems.

Recommended implementation:

iOS:
Apple In-App Purchases

Android:
Google Play Billing

Cross-platform subscription management:
RevenueCat

RevenueCat can simplify:

  • Product configuration
  • Receipt validation
  • Subscription status
  • One-time purchases
  • Cross-platform supporter status
  • Webhooks
  • Revenue analytics

Recommended product setup:

One-time products:
support_1
support_5
support_10
support_25

Monthly products:
support_monthly_1
support_monthly_299
support_monthly_5
support_monthly_10

Important:

  • Verify current App Store and Play Store rules before launch.
  • Contributions inside the mobile app may need to use Apple/Google billing.
  • External donation links may have restrictions depending on region, app category, and legal structure.
  • Do not present contributions as charitable donations unless WalkSafe is legally registered as a nonprofit or charity.

Use wording like:

Support WalkSafe

Instead of:

Donate to charity

Unless the legal structure supports that claim.

Revenue Tracking

WalkSafe should track monetization without invading user privacy.

Important metrics:

Monthly active users
Completed trips
Support screen views
Contribution conversion rate
Average contribution amount
Monthly recurring contribution revenue
One-time contribution revenue
Supporter retention
Supporter cancellation rate
Percentage of server costs covered

Do not track unnecessary personal location data for monetization.

Example internal metrics:

MAU: 10,000
Supporters: 420
Supporter rate: 4.2%
Average monthly contribution: €2.80
Monthly supporter revenue: €1,176
Server cost coverage: 64%

Transparency Dashboard

A transparency dashboard can increase trust and encourage support.

Possible in-app dashboard:

WalkSafe this month

Active users:
12,480

Completed safety trips:
48,920

Supporters:
614

Server costs:
€1,240

Covered by supporters:
€870

Coverage:
70%

This makes contributions feel concrete.

The dashboard should avoid exposing sensitive personal data.

Good metrics:

  • Total completed trips
  • Total supporters
  • Server costs
  • Percentage of costs covered
  • Number of users helped

Avoid:

  • Individual locations
  • Personal movement data
  • Specific emergency details
  • Sensitive trip patterns

Risks and Mitigations

Risk 1: Revenue is unpredictable

Pay What You Want can be less predictable than subscriptions.

Mitigation:

  • Offer monthly contributions
  • Show recommended amount
  • Show transparent costs
  • Encourage recurring support
  • Add institutional sponsorship later if needed

Risk 2: Too many users choose €0

This is expected.

Mitigation:

  • Design for low infrastructure cost
  • Use own routing server
  • Optimize Firebase reads/writes
  • Avoid expensive third-party APIs
  • Ask for support after users experience value

Risk 3: Users do not understand why support is needed

Mitigation:

  • Explain server costs clearly
  • Show real cost transparency
  • Use honest copy
  • Show impact of supporters

Risk 4: App store payment complexity

Mitigation:

  • Use RevenueCat
  • Keep product tiers simple
  • Validate receipts server-side
  • Check store policies before launch

Risk 5: Users think payment gives better safety

Mitigation:

  • Clearly state all safety features are free
  • Avoid premium language
  • Use “supporter” instead of “premium”
  • Do not restrict emergency functionality

Launch Strategy

Phase 1: Launch with Free + Support Screen

At launch:

All features are free.
Support WalkSafe is available in Settings.
No forced payment prompts.

Phase 2: Add Soft Prompts

After the product has value:

Show support prompt after safe arrival
Show support prompt after 5 completed trips
Show monthly transparency update

Phase 3: Add Supporter Recognition

Add:

Supporter badge
Founder Supporter status
Optional supporter wall
Thank-you messages

Phase 4: Add Recurring Contributions

Add:

€1/month
€2.99/month recommended
€5/month
€10/month

Phase 5: Add Institutional Sponsorship Later

Even if the main model remains Pay What You Want, WalkSafe can later accept sponsorships that do not affect users.

Examples:

University sponsors WalkSafe for students
City sponsors safer night routes
Event sponsors WalkSafe for visitors

This should not change the user model. Users still pay what they want.

Long-Term Strategy

The long-term goal is to make WalkSafe financially sustainable without becoming exploitative.

The ideal long-term monetization structure:

User contributions:
Pay What You Want

Community support:
Founder supporters and monthly supporters

Optional institutional support:
Schools, universities, cities, events, and safety partners

No ads.
No location data sales.
No premium safety paywalls.

WalkSafe should become known as:

The safety app that stays free because people support it voluntarily.

This can become a competitive advantage.

Summary

WalkSafe monetization is based on one core model:

Pay What You Want

Users can pay:

€0 or any amount they choose

All core safety features remain free.

WalkSafe earns money through voluntary support, not by restricting safety.

The positioning is:

WalkSafe is free because safety should be accessible to everyone.
Pay what you want to help keep it running.

Core rules:

No ads.
No selling location data.
No premium safety features.
No forced subscription.
No guilt-based payment.

Supporters receive recognition, not better safety.

This model protects trust, supports the mission, and keeps WalkSafe accessible to everyone.

Current Decision

WalkSafe will launch with:

100% free app access
Pay What You Want contribution model
€0 option always available
Optional monthly and one-time support
No feature paywalls
No advertisements
No location data monetization

Next implementation step:

Design and build the Support WalkSafe screen.
Add one-time and monthly supporter products.
Store supporter status in Firebase.
Keep all safety features available to every user.