Sip
Sip was Product Hunt's mobile and web app for daily tappable tech news and startup stories.
View original storyProduct snapshot
What it was
Sip delivered short, tappable tech news and product stories through a mobile app and later the web.
Who it was for
Problem / value
Give Product Hunt readers a compact, low-noise way to catch up on important tech stories.
Core workflow
- read summarized tech stories
- follow product launches
- consume tappable news cards
- share lightweight tech updates
Product form
Pricing model
Free content product; no public paid model found in the sources used.
What happened
Summary
Product Hunt discontinued Sip in January 2019 after launch attention and reader growth failed to create sustainable standalone adoption.
Outcome
Sip shut down as a standalone product; its main public lesson is that content products need native distribution and retention loops.
Demand signal
Product Hunt reported that Sip reached meaningful readership, but web growth cannibalized other Product Hunt channels and did not lead to sustainable adoption or retention.
Distribution issue
Sip depended heavily on Product Hunt's existing homepage, newsletter, and social channels, so growth could move attention around instead of adding durable new demand.
Timeline
- Late 2017: Product Hunt began exploring a new way to deliver tech news and stories.
- 2018-02: Sip launched on Product Hunt and became #1 Product of the Day.
- 2018-07: Sip reached 9.4K unique monthly readers, according to the postmortem.
- 2018-08: The team expanded Sip to the web and readership grew, but much of the traffic came from Product Hunt channels.
- 2019-01: Product Hunt quietly discontinued Sip.
Before you build
Why it matters
Many newsletters, directories, AI digests, and media side products launch from an existing audience and misread attention as standalone demand.
Primary check
Prove a standalone distribution loop and repeat reading habit before turning an existing audience into a separate content product.
Checklist
- Does the product grow without homepage, newsletter, or founder-audience promotion?
- Do readers return without a push notification or parent-channel reminder?
- Does the new product increase total business value instead of shifting attention?
- Track how many users arrive from a source that would not otherwise visit the parent product.
- Measure repeat reading by cohort, not only monthly readers.
- Define the sharing or contribution loop before scaling content operations.
- Estimate weekly editorial cost before treating the product as a small side project.
Relevant if
- You are building a newsletter or curated digest
- You are launching from an existing audience
- Your main metric is readers, upvotes, or traffic
Less relevant if
- The product already has organic sharing loops
- The new product clearly adds revenue or retention to the parent business
Pre-build tests
- Run a manual digest for a small audience and measure repeat opens over several weeks.
- Launch without using the parent homepage or newsletter and compare retention quality.
- Test a built-in sharing or submission loop before building a full app.
Transferable lessons
- Separate launch applause from repeat habit.
- Measure additive growth, not just traffic shifted from another channel.
- Build distribution into the product before investing in more content operations.
If you build this today
Start with one repeatable content habit, one native sharing loop, and one additive traffic source before expanding formats or moving traffic from the parent platform.