SipLeague

SipLeague guide

Build a useful drink memory

A drink history becomes more useful when “I tried it”, “I would choose it again” and “I rate it highly” are treated as different signals instead of being collapsed into one public review score.

Three signals, three jobs

Save means a drink belongs in your personal history or shortlist. Favourite is deliberately stronger: it means you would actively choose that drink again. 1–5 Rating records your own preference on a consistent scale.

SipLeague keeps these interactions structured rather than opening a free-form public review feed, so personal history remains easy to filter and compare.

Curated drinks and packaged products are different records

SipLeague uses two distinct identifiers because the information comes from different sources and changes in different ways. Editorial drink guides use stable curated slugs such as espresso-martini. A packaged bottle or can uses its barcode. The two should never overwrite one another simply because their names look similar.

Curated drink

Editorial information such as style, ingredients, preparation context and related guides. These records use SipLeague slugs and can be useful without an account.

Packaged product

A specific retail product identified by barcode. Catalogue details may come from Open Food Facts, while your Save, Favourite and Rating state belongs to your SipLeague account.

Why the separation matters

A Mojito guide and a canned mojito product are not the same thing. The guide can explain the style. The barcode record can identify a specific brand and package. Your personal history can include either or both without one replacing the other.

Curated My Sips state can therefore be keyed by a SipLeague slug, while packaged My Sips state is keyed by barcode. Account migration can move each record into the correct store instead of guessing from a product name.

What stays on your device

SipLeague can keep a bounded local cache of previously viewed packaged-product catalogue details so a recently scanned item can still be recognised during a temporary network problem. That catalogue cache is separate from account-backed My Sips state.

If you switch accounts, the previous account’s packaged Save, Favourite and Rating state should disappear before the replacement account is hydrated. The local Open Food Facts lookup cache can remain because it is catalogue data, not another person’s private My Sips history.

Open Food Facts attribution

Packaged-product catalogue information may be sourced from Open Food Facts. SipLeague preserves source attribution and treats those fields as catalogue data. Personal Save, Favourite and Rating values are separate SipLeague account state.

A simple habit that stays useful

  1. Save a drink when it belongs in your history.
  2. Rate it only after you have enough experience to form your own preference.
  3. Use the same 1–5 meaning across categories.
  4. Mark Favourite only when you would actively seek it again.
  5. Use My Sips filters instead of relying on memory or public comments.

Keep venue memories factual

Remembering where you encountered a drink can be useful, but a past visit is not proof that a venue still stocks the same product today. SipLeague keeps stable venue identity separate from fast-changing claims such as current stock, opening hours or access.

Next steps

Use the barcode drink scanner, explore public drink discovery, or open My Sips. For a repeatable scoring method, read Rate drinks consistently.