Inspiration

Samsung keeps changing where your content lives. Gallery sync moved from Samsung Cloud to OneDrive about five years ago, then OneDrive support ended on September 30, 2026, and press reports say Google Photos is replacing it. Samsung Notes lost its OneNote sync after July 2026. Samsung's own notice warned that synced photos would disappear from Gallery, including on Samsung TVs and Family Hub appliances.

For someone with a phone, tablet, and laptop, that means no stable answer to "where are my photos and notes?" Forum posts going back to 2020 show people losing photos or struggling to fix sync after earlier switches. We realized the friction isn't storage. It's uncertainty.

What it does

Galaxy Anchor is one library for photos, notes, and files that pulls content from every connected cloud and device into a single place, so users never need to know which provider holds it.

  • Unified browse: photos, notes, and files from every connected source in one view
  • Source visibility: every item shows where it lives
  • Device availability: see what is and isn't available on your phone, tablet, Galaxy Book, and TV
  • Built for provider changes: the product is designed to keep content reachable when Samsung or the user switches clouds

The MVP is read-only where possible, so it can't delete or overwrite anything.

How we built it

  • Research: Samsung's own notices, Microsoft's support page, press coverage, and Samsung Community forum threads. We labeled forum evidence as self-reported, since we had no usage data.
  • Product docs: problem statement, proto-personas, journey map, success metrics, MVP plan, and a full PRD
  • Prototype: a high-fidelity, clickable prototype of the core flows, built in [Figma Make / Figma], and shown in our demo video
  • Differentiation: we compared our approach with Apple's iCloud model, using Apple's support pages
  • We used AI tools to speed up research synthesis, drafting, and prototype generation, and we checked the claims ourselves.

Challenges we ran into

  • Thin evidence. We had Samsung notices, press, and forum posts, but no usage data, so we had to label our claims as hypotheses.
  • Shifting facts. Samsung hadn't formally announced the Google Photos replacement when we researched, and reports differed, so we avoided claiming anything we couldn't confirm.
  • Dependencies we don't control. Samsung's options depend on its deals with Google and Microsoft. That pushed us toward a provider-neutral, read-only design.
  • Choosing one problem. We started with four ideas (cross-device sharing, cloud storage, AI session setup, device role switching) and picked the one with the strongest, most verifiable evidence.
  • A tight timeline. We had to cut features and polish to finish the PRD, deck, prototype, and video.

Accomplishments that we're proud of

  • A problem backed by Samsung's own documentation, not just opinion
  • A clear difference from Apple: iCloud is consistent but tied to one first-party cloud, while Galaxy Anchor offers one library with open provider choice
  • Honest labeling throughout. Our deck and PRD mark hypotheses and unvalidated assumptions, and we caught and fixed several of our own overstatements.
  • A full submission: PRD, pitch deck, prototype, and demo video

What we learned

  • Start with the user's problem before the feature. Our first draft jumped to solutions, and the evidence pushed us to a different problem.
  • Evidence needs checking. Dates, quotes, and claims changed as we verified them.
  • Honest limits make a pitch stronger. Saying "targets TBD after validation" is better than making up numbers.
  • Differentiation has to be specific. Apple's one-cloud model is a real advantage, so our edge had to be something it doesn't do.

What's next for Galaxy Anchor

  • Run our survey and a prototype usability test with multi-device Galaxy owners
  • Check whether users care about cross-device access or only backup
  • Confirm what Google Photos and OneDrive allow for read-only access
  • Pilot on a limited set of devices and providers

Built With

  • canva
  • chatgpt
  • claude
  • docs
  • figma
Share this project:

Updates

Submission history