Post page share placements

Every placement the Storybook post-page page argues for, with working controls instead of pictures of them. Each copy button really copies; each Snapshot really rasterizes the card it would share.

Every control below is the production component, wired to the real post page. On a branch preview all of them are on, so open any post on this deployment and they are there — no GrowthBook needed. On app.daily.dev each sits behind its own flag: snapshot_selection_share, post_copy_summary, post_share_prompts, poll_snapshot and post_nav_copy_link, all defaulting to off.

The two additions

Two payloads on this page stand alone without the article: the summary we generated and a line the reader chose. The summary goes out as text so it can be pasted into a thread; the selection goes out as an image, because a quote is worth looking at.

Recommended · workingCopy summary — a tiny icon at the end of the TLDRPress it: the clipboard gets the headline, the summary and the link as three paragraphs. Icon only and XSmall, so it reads as punctuation on the paragraph rather than a button under it.
XDA Developers

Why iconic tech brands lost their dominance

Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to.

Recommended · workingFloating bar on selected textDrag-select any part of the paragraph. The bar follows the quote; Snapshot puts the PNG on your clipboard, or downloads it where the clipboard refuses images. This is the one placement already wired into the real post page.
XDA Developers

Why iconic tech brands lost their dominance

Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to.

ResultWhat the selection exportsThe card at every passage length, and the real capture underneath — this is the file, not a preview of it.
one line

They optimised the product they had.

XDA Developers
a sentence

Every one of them optimised the product they had instead of the one their customers were moving to.

XDA Developers
a passage . the frame grows

Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to.

XDA Developers
past 900 chars . cut at the last word

Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to. Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to. Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to. Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to. Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers…

XDA Developers

The prompted moments

Three controls that appear on their own rather than waiting to be found, all additive to the action bar. Copy link works in each; the named targets and squad avatars are inert, since what is under review is where the control sits.

Share stripShare strip under the comment barDiscussionShareRow, already shipping in the discussion panel but not on the post page. The densest share affordance we have: named targets and squads, no menu, no modal, directly under the composer.
Share your thoughts
End of threadBand under the last commentPeak-end: it sits where reading actually stops, and copy link is the whole offer — a still image of a live thread goes stale within hours.
Bobby IlievThe org chart point is the whole article, honestly.
After upvote · shippingPrompt after an upvote — already shipsPostContentShare renders this the moment you upvote a post, with a copy-link input rather than a button. Nothing was built for it: the Storybook page proposed a placement production already had. Snapshot stays out either way — it would be the payload the post's own OG image already carries.

The recommendation: put snapshot on the poll

Of the eleven post types this is the one where snapshot beats a link outright: the result is a bar chart, self-contained and visual, and worthless as a URL once voting closes. Both Snapshot buttons below capture the poll card for real.

Recommended · workingSnapshot beside the vote countIcon only, on the metadata line under the bars, where the eye already lands after reading the result.

Which do you reach for first in a new service?

Postgres62%
Redis21%
SQLite11%
Something else6%
1,284 votes · 2 days left
Push · workingSnapshot on the post-vote promptThe same payload one moment later, on the prompt that already appears after voting — labelled and primary here, because the prompt is the offer.
Why did you vote this way?
ResultWhat the poll exportsThe winner is drawn in the accent and the rest stay quiet, so the answer reads before the bars do.
Poll result · 1080 square
Poll

Which do you reach for first in a new service?

  1. Postgres62%
  2. Redis21%
  3. SQLite11%
  4. Something else6%
Frontend Fans

The sticky nav

The sticky nav appears on scroll and carries the post title and its controls. It is a share slot nobody uses — one copy-link icon is the whole recommendation, and snapshot stays out of it.

Sticky nav · workingOne copy-link icon in the sticky navBeside the existing controls, at the same size as its neighbours.
Why iconic tech brands lost their dominance

What ships today

Two share affordances already exist on the post page and neither needs building — open any real post to try them. They are here so the additions above are judged against what is already there rather than against nothing.

TodayThe ⋯ menu opens with Share via, and the bar ends with CopyCopy link in the action bar is live below — the same action the production bar performs. The ⋯ menu and its share sheet are inert here; they already work on a real post.
XDA Developers

Why iconic tech brands lost their dominance

Nokia, BlackBerry and Kodak all led their categories and all missed the same turn. Every one of them optimised the product they had instead of the one their customers were moving to.