Objectuve Docs

Appearance

Our Story — In-App Support Page PRD ​

Product: Objectuve (codename: Enkidu) Feature: In-app "Our Story" page — mission narrative + support encouragement Status: Shipped — May 2026 Date: April 2026

1. Problem Statement ​

Objectuve has a marketing site about.html that tells the company's story to prospective users. But once someone is inside the app, there is no way to learn why the product exists, what it stands for, or how to support its continued development. The existing in-app Supporter touchpoints (Settings tab, streak nudges, badge modal prompts) jump straight to "here are the perks" without providing context about the mission those perks fund.

Three problems:

  1. No origin story inside the product. Users who discover Objectuve through the app store or a friend's link may never visit the marketing site. The "why" behind the product — anti-social design, PBC structure, the 10-year journey — is invisible to them.

  2. Support prompts lack context. The current Supporter upgrade flow (modal with plans and prices) is transactional. It lists cosmetic perks but doesn't connect paying to funding something the user believes in. Users who'd happily support a mission they care about are never given the mission.

  3. No organic support path. There is no in-app mechanism to spread the word. Users who love Objectuve but don't want to pay have zero way to help — no share flow, no referral prompt, no "tell a friend" affordance.

This page solves all three: it tells the story inside the product, frames Supporter as mission funding (not a purchase), and gives every user — paying or not — a way to help.

2. Goals & Success Metrics ​

Primary Goals ​

  1. Give every user access to Objectuve's origin story, philosophy, and commitments inside the app
  2. Increase Supporter conversion by providing mission context before showing plans
  3. Create an organic sharing path for users who want to support without paying

Success Metrics ​

MetricTargetMeasurement
Page visits (weekly active users who visit /our-story at least once)15%+ within 90 daysPlausible/analytics page view
Supporter conversion rate for users who visited Our Story vs. didn't+20% liftCohort comparison
Share button taps5%+ of page visitorsEvent tracking on share/copy action
Time on page60–120 secondsAnalytics; too low = not reading, too high = violates anti-social principle

Guardrails ​

  • The page must not feel like a sales pitch. It tells a story; the support CTAs come after the story, not before.
  • No pop-ups, no urgency language, no "limited time" framing. This is a Public Benefit Company page, not a conversion funnel.
  • Supporters who visit should feel thanked, not re-sold. The page adapts — gratitude replaces the upgrade prompt.
  • Page should be readable in under 2 minutes.

3. User Stories ​

  • US-1: As a user, I want to learn why Objectuve exists and what it stands for, so I can decide if its mission aligns with my values.
  • US-2: As a non-supporter, I want to understand what my support would fund (not just what perks I'd get), so paying feels like backing a mission, not buying a product.
  • US-3: As a user who doesn't want to pay, I want a way to share Objectuve with someone who might benefit, so I can support the project organically.
  • US-4: As a Supporter, I want to feel recognized when I visit this page, not prompted to buy something I already have.
  • US-5: As a new user, I want to discover this page naturally through the sidebar, so I can learn the story when I'm curious — not have it pushed on me.

4. Page Design ​

4a. Route & Navigation ​

Route: /our-story (protected, requires authentication)

Entry points:

  • SideMenu footer: The existing "Support" link (gold heart icon, visible only to non-supporters) changes destination from /settings?tab=supporter to /our-story. Same icon, same label, new destination.
  • Settings Supporter tab: Below the existing "View Plans" button in the non-supporter card, add a text link: "Learn why we built Objectuve" → /our-story.
  • Direct URL: Any logged-in user can navigate to /our-story directly.

Not added to: Bottom tab bar (too prominent for a story page), Dashboard (should be discovered, not pushed), onboarding wizard (too early — user hasn't used the product yet).

4b. Page Sections ​

The page is a single scrollable view. No tabs. Sections flow top to bottom like a short essay.

Section 1: Hero ​

No card. Centered text on the page background.

  • Headline: "Why We Built This"
  • Lead paragraph: The core belief — the hardest part of achieving anything isn't knowing what to do, it's staying consistent when no one's watching. We built an app that makes showing up feel good, then gets out of your way.
  • Tone: Direct, warm, personal. Like the opening of a letter.

Section 2: The Story ​

Card component. Prose narrative.

  • Heading: "How It Started"
  • Content: Conversational retelling of Objectuve's journey:
    • The social media envy insight — seeing someone's highlight reel vs. being brought along on the journey
    • The V1 in 2019 — thousands of goals created, the core idea resonated
    • The quiet years — technology wasn't ready, the philosophy wasn't clear enough
    • The anti-social app philosophy taking shape during the hiatus
    • The 2024 rebuild from scratch, filtering every decision through "does this help the user or help our metrics?"
    • The 2026 relaunch
  • Tone: Honest, reflective. Acknowledge the messy parts. Not a polished corporate origin myth — a real story about an idea that took a decade to get right.
  • Length: ~150–200 words. Readable in 60 seconds.

Section 3: What We Believe ​

Card component. Four values as short prose blocks (not bullet points).

  • Heading: "What We Believe"
  • Values:
    1. Respect your time — 10 minutes a day. Quick check-in, real feedback, done. If you're spending more than that, something's wrong — and we'll tell you.
    2. Progress is earned — Every streak, badge, and XP point comes from real effort. No vanity metrics, no manufactured dopamine.
    3. Free means free — Full access for individuals, forever. No ads. No data selling. The Supporter tier is cosmetic-only.
    4. Community for accountability — Social features exist so people feel seen and supported, not entertained. A "like" on Objectuve means "I see you doing the work."

Section 4: Our Commitments ​

Card component. Icon + one-line pairs in a 2-column grid (1 column on mobile).

  • Heading: "Our Commitments"
  • Six commitments:
    1. No ads, ever
    2. No data selling
    3. Free for individuals, forever
    4. Your data is yours (export + delete anytime)
    5. Public Benefit Company (legally enforceable, not just marketing)
    6. Intentional engagement limits (~10 min/day by design)

Section 5: How You Can Help ​

Two cards in a responsive grid (side by side on md+, stacked on mobile).

Card A — Become a Supporter (conditional rendering based on isSupporter):

Non-supporters:

  • Brief explanation: Supporter funds independent development. It's not a premium tier — it's a way to back the mission.
  • Perks listed briefly: 9 custom themes, profile badge, early access to features
  • Explicit note: "Every feature works without paying. Supporter is purely cosmetic."
  • CTA button: "View Supporter Plans" → opens existing SupporterUpgradeModal
  • Gold accent border on the card

Supporters:

  • Gratitude message with their SupporterBadge displayed
  • "You're helping keep Objectuve independent. Thank you."
  • No upsell, no cross-sell. Just thanks.

Card B — Spread the Word (always visible):

  • "Tell someone who has a goal they care about."
  • Share button using Web Share API on supported platforms, clipboard copy fallback on desktop
  • Share URL: https://www.objectuve.com
  • Share text: "Objectuve — a goal tracker that wants you to close it. Free forever."
  • Toast confirmation on successful copy

Muted text, centered. Not a card.

  • "Objectuve Softworks, LLC — Public Benefit Company, Chicago" (Delaware Public Benefit LLC; principal office in Chicago, IL)

4c. Supporter State Awareness ​

The page always renders the full story. Only Section 5 Card A adapts based on supporter status:

StateCard A Renders
Not a supporterMission pitch + "View Supporter Plans" button
Monthly/Yearly subscriberGratitude + SupporterBadge
Lifetime supporterGratitude + SupporterBadge (lifetime variant)

Supporter state comes from USER_QUERY via the existing useClerkSync pattern (same as Settings.vue and SideMenu.vue).

5. Technical Approach ​

New Files ​

FilePurpose
ionic_frontend/src/views/OurStory.vueThe page view

Modified Files ​

FileChange
ionic_frontend/src/router/index.tsAdd /our-story route (lazy-loaded)
ionic_frontend/src/components/SideMenu.vueChange "Support" link from /settings?tab=supporter to /our-story
ionic_frontend/src/views/Settings.vueAdd "Learn why we built Objectuve" link in non-supporter card

Components Reused (no new components) ​

  • AppHeader — page header with back navigation
  • Card, CardHeader, CardTitle, CardDescription, CardContent — section containers
  • SupporterUpgradeModal — checkout flow (opened via ref)
  • SupporterBadge — displays supporter tier badge
  • UiButton — action buttons

Data Dependencies ​

  • USER_QUERY (existing) — provides isSupporter, supporterTier, supporterUntil
  • useClerkSync composable — gates the query on user sync completion
  • No new GraphQL queries or mutations required

6. Content Principles ​

These guide the writing of actual page copy during implementation:

  1. Story first, ask second. The support CTAs come in Section 5. Sections 1–4 are pure narrative. A user should feel informed before they feel asked.

  2. Honest > polished. Acknowledge the hiatus, the false starts, the years of quiet. This isn't a startup that appeared overnight with a pitch deck — it's a decade-old idea that finally found its form.

  3. Specifics > platitudes. "10 minutes a day" is better than "respects your time." "No ads, ever" is better than "we value your privacy." Name the commitments concretely.

  4. Gratitude > guilt. For supporters: pure thanks. For non-supporters: the share path is presented as equally valuable. There is no "if you really cared you'd pay" subtext.

  5. Brand voice. Coach who's also a friend. Playful, not childish. Empowering, not generic-motivational. Brief — one sentence when one sentence works.

7. Out of Scope (for now) ​

  • Referral codes or tracked referral links (future: engineering-referral-loops)
  • Social sharing to specific platforms (Twitter, Facebook buttons)
  • Impact dashboard ("your support has funded X hours of development")
  • Video or animated storytelling
  • Localization / i18n

8. Open Questions ​

  1. Should the SideMenu "Support" link remain visible for Supporters? Currently it's hidden when isSupporter is true. If this page is now about the story (not just upgrade), showing it to everyone could make sense — but it changes the sidebar contract.

  2. Should we track page visits as a UserAction for gamification? Probably not — reading about the mission shouldn't be a badge trigger. But worth confirming.

  3. Should there be a link from the marketing about.html to the in-app version? For logged-in users who land on the marketing site, a "Read the full story in-app" link could work. Deferred to a future pass.

Last updated: 2026-05-23

Loading…