Skip to content

Landing page has no mention of the mobile app — missing App Store/Play Store links, screenshots, and messaging #139

Description

@ibn0n

Problem
The gib.work landing page (https://gib.work/) never mentions that Gibwork has a live mobile app, even though it’s published on both stores:
• iOS: https://apps.apple.com/us/app/gibwork/ (linked from @gib_work’s X profile)
• Android: https://play.google.com/store/apps/details?id=com.gibwork.app
The Play Store listing describes real, current functionality — discovering bounties, submitting work, tracking submissions, and managing payouts from a phone — and has active user reviews. None of that appears anywhere on the marketing site.
Right now the entire landing page funnels every visitor to “Open App” (app.gib.work), a desktop web app. A visitor who’d rather work from their phone has no way to discover the app exists unless they already follow Gibwork on X or happen to search the app stores directly. That’s a conversion gap for exactly the audience — bounty hunters who want to check tasks on the go — the app was built for.
Beyond the app gap, the current page also undersells what Gibwork actually is:
• The hero framing (“Find Talent, Find Work”) reads as a generic freelance marketplace. The three “Get help from an expert” cards (Open Source Bounty / Simple Task / Services) don’t reflect the breadth of live task categories (social media, content, design, dev bounties in JS/Rust/TypeScript, UX feedback, etc.) visible on app.gib.work.
• The Testimonials section has a heading (“Hear what our users have to say”) but no visible testimonial content on the static page.
• The footer only links to a Privacy Policy PDF — there’s no Terms of Service link, despite the app’s own signup flow referencing “Terms of Service and Privacy Policy.”
Recommended Solution

  1. Add a mobile app section to the landing page, placed after the “Get help from an expert” section and before Testimonials:
    • Section heading: “Take Gibwork with you”
    • Subhead: “Browse bounties, submit work, and track payouts from your phone.”
    • App Store and Google Play badges linking directly to the two store listings above
    • 2–3 screenshots or a short device mockup showing the bounty list and submission flow (can be pulled from the Play Store listing’s existing screenshots as a placeholder, or re-shot from the app)
  2. Add app badges to the header/hero as a secondary CTA, next to “Open App” — something like “Get Started For Free” (web) / small App Store + Play Store icons (mobile), so both paths are visible above the fold.
  3. Refresh the “Get help from an expert” card copy to reflect actual task diversity, e.g. swap or add a fourth card: “Social & Content Bounties — Threads, posts, and marketing tasks for Web3 projects,” since social/content tasks are a large share of what’s live on the platform today.
  4. Add a Terms of Service link to the footer, next to Privacy Policy.
    Why this improves the landing page
    • Closes an actual conversion gap: mobile-first users currently bounce because there’s no visible path to the app.
    • Brings the marketing site in line with the current product (the task description explicitly calls out “mobile app” as something the page should reflect).
    • More accurate category cards set correct expectations before signup, reducing early drop-off from users expecting a narrower “freelance marketplace” than what’s live.
    • Small, scoped, non-breaking changes — no redesign, just closing gaps between the live product and the marketing page.
    Suggested implementation notes (for whoever picks this up)
    • App store badge SVGs are freely available from Apple’s and Google’s official brand asset kits.
    • Screenshots should be pulled fresh from the current app build rather than reused Play Store images long-term, since store screenshots can lag behind app updates.
    • Section should be responsive: badges stack vertically on mobile, sit side-by-side on desktop, consistent with the rest of the page’s existing breakpoint behavior.
Image Image Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions