App demo
Hollingsworth CardHollingsworth Home & Kitchen, Madison
Show it at the register
The one motion the app exists for: open it, hold the number under the reader, done — including down in the basement, where no signal arrives.
- In the hands of
- Cardholder since 2019
- Shown on
- iOS — title centred, swipe bar below
- Replaces
- Replaces the plastic card left at home on the day you shop — otherwise the register has to key the number in by hand —, the flyer that lands three days after the offer has run out, and the hunt through the kitchen drawer for a receipt. Without one the register takes nothing back after fourteen days; in the app it is still legible two years on.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
Hollingsworth Home & Kitchen, Madison is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
Hollingsworth Home & Kitchen runs three shops and a points scheme. The card lives in a wallet and is at home precisely when somebody drops in on impulse; the leaflet through the letterbox does not reach the person currently looking at frying pans; and the receipt needed for a return is somewhere in a pile of paper. Three small frictions, each of which costs either a sale or a conversation at the till.
Decisions
The card lives on the device and opens without a signal
It is the reason the app stays installed. A card that shows a spinner in the basement gets shown at the till exactly once — after that the plastic comes back.
Points, not baskets
The device shows how many points a purchase earned and which shop it was in. What was in it appears only on the receipt the customer opens herself. Anyone issuing a loyalty card should write that difference down rather than bury it in a privacy notice.
Tier and voucher are kept apart
One depends on annual spend, the other on the points balance. A single bar labeled “loyalty” would look tidier and would blend two different promises into one the business cannot keep.
Deliberately left outNo location access and no redemption in the app. For three shops the ZIP code from the profile is enough; asking for a location would be out of proportion to the purpose. And a voucher the app cancels itself is a payment transaction with everything that entails — redemption happens at the till.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 16
- Languages
- 4
Navigation responds, including the route from the purchase list into a single receipt and back. The card, the offer list and the redemption flow are fully rendered and inert; the stripe pattern on the card is schematic and carries no readable identifier. The four states have a view of their own.
How it would go on
Connection to the till system
Points are earned at the till, vouchers are canceled there, receipts are created there. Without that path the app shows a balance nobody maintains.
Scheme and terms
Points rate, expiry, tiers, voucher value, exclusions. The business sets those, and they end up in scheme terms somebody has to write and stand behind.
Consent and retention
A loyalty scheme processes purchasing behavior. What is stored, for how long, what needs consent and how a customer withdraws it belongs before launch, not in the small print afterwards.
An app like this for your business?
Hollingsworth Card is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.