Remix

Make your own version of Keeply Purchase Tracker

Get an exact, working copy in your account, then change anything with chat.

Original by big boy

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build the foundation and core features of my web app, Keeply. This prompt covers the design, dashboard, purchases, receipts, product images, returns, warranties, reminders, AI receipt scanning and currency detection.

1. Design and branding

Create a premium, modern, professional app with a clean Apple-inspired design.

Use this exact colour palette:

* Background: #F8FAFC
* Main text: #1F2937
* Teal: #0F766E
* Mint/sage: #D1FAE5
* Cards: #FFFFFF
* Amber for approaching deadlines
* Red for overdue or urgent items
* Muted grey for secondary text and subtle neutral borders

Set light mode as the default. Add a dark-mode toggle in the top-right corner and save the user’s theme preference. Dark mode must be comfortable to use, without harsh white backgrounds.

Use smooth animations, including fade-up scroll reveals, staggered cards and subtle transitions. Respect reduced-motion accessibility settings.

Use this exact homepage content:

* Hero pill: “SMALL HABIT. BIG PEACE OF MIND.”
* Heading: “A little less worry, a lot more organised.”
* Subtitle: “Your purchases, receipts and peace of mind — all in one place.”
* Primary button: “+ Add purchase”
* Secondary heading: “Keep the things you love. We’ll keep the details.”
* Supporting text: “No more lost receipts or missed return windows. Just everything you need, right when you need it.”
* Link: “Explore your receipts”
* Include a premium receipt illustration with “keeply.” and a floating notification reading “One less thing to remember.”

2. Navigation

Create a responsive navigation menu with:

* Home/Dashboard
* My Receipts
* Purchases
* Returns
* Warranties
* Reminders
* Settings

Make all links functional. Ensure the layout works on phones, tablets and desktops.

3. Dashboard

Create a dashboard driven by real saved user data, not hard-coded demo figures. Include:

* Total purchases and spending
* Recent purchases and receipts
* Upcoming return deadlines
* Upcoming warranty expirations
* Reminders
* Spending charts and category breakdowns
* Quick-action buttons

Update dashboard figures immediately when the user adds, edits or deletes records. Handle different currencies correctly.

4. Purchases

Build a complete purchase management system. Users must be able to add, view, edit, delete, search, filter, sort and organise purchases.

Each purchase should support:

* Product name, image, brand and retailer
* Purchase date and price
* Original currency
* Category and quantity
* Receipt attachment
* Order reference
* Return deadline
* Warranty start and expiry dates
* Serial number or model number
* Notes and status

Validate forms and save everything to persistent storage so data remains available after refreshing or signing in again.

5. Receipts

Create a receipt library that supports:

* Uploading images and PDFs
* Taking a receipt photo using a phone camera where supported
* Previewing, editing, downloading, replacing and deleting receipts
* Searching, filtering and sorting receipts
* Linking receipts to purchases
* Preserving the original uploaded file

Use secure file storage and ensure users can only access their own receipts.

6. Product images

When a user enters a product, try to retrieve an accurate image using a properly configured product catalogue or API. Prefer the exact model, then a manufacturer or retailer image.

If no reliable image is available, use a suitable category illustration or neutral placeholder. Never pretend an unrelated image is the exact product.

Avoid sending API searches on every keystroke. Cache results, show loading states and handle unavailable services gracefully. Explain any API configuration required.

7. Returns

Create a return tracker with these statuses:

* Upcoming
* Due soon
* Returned
* Completed
* Overdue

Display countdowns and clear warnings using amber for approaching deadlines and red for overdue returns.

Allow users to enter and edit return deadlines. Use externally sourced deadlines only when the source is reliable, and never invent a retailer’s return policy. Add configurable reminders.

8. Warranties

Allow users to record:

* Product and retailer
* Warranty start and expiry dates
* Receipt
* Serial/model number
* Warranty documents
* Notes

Display active, expiring and expired warranties. Never invent warranty terms or expiry dates.

9. Reminders

Allow users to create, edit, complete and dismiss reminders. Include return and warranty reminders.

Implement actual notifications or scheduled delivery only where supported by a real configured service. Do not claim that a notification or email was sent unless delivery is confirmed. Provide clear permission and setup instructions where necessary.

10. AI receipt scanner — Keeply Pro

Build a real AI-powered receipt scanner for images, PDFs and camera captures.

Extract information when visible, including:

* Retailer and address
* Date and time
* Products and quantities
* Individual prices and discounts
* Subtotal, tax/VAT and total
* Currency
* Payment method, but only if shown
* Transaction reference
* Return or warranty terms only when printed on the document

Show an editable review screen before saving. Flag uncertain information and never invent missing fields. Ask the user to confirm extracted details and any suggested return or warranty deadlines.

Detect possible duplicate receipts, preserve the original file, and save confirmed details as actual database records. Update the dashboard and search results.

Implement real OCR/AI integration with appropriate loading, error and retry states. Keep API keys and secrets on the server. Explain which provider must be configured and whether usage may cost money. Do not simulate a working AI scanner if no real integration exists.

11. Currency detection

Detect the user’s country using a privacy-conscious method; GPS is not required. Use GBP for the UK and other places that officially use sterling, and the appropriate local currency elsewhere.

Requirements:

* Store currencies using proper ISO codes such as GBP, USD and EUR.
* Provide a manual currency preference in Settings.
* Let manual preferences override automatic detection and persist across sessions.
* Preserve each purchase’s original amount and currency.
* Do not simply replace a currency symbol while leaving the amount unchanged.
* Use a reliable exchange-rate source if conversion is needed.
* Do not add together different currencies as though they were the same. If conversion is unavailable, show separate totals by currency.

12. Technical requirements

Use a persistent database and secure file storage. Create appropriate data models for users, purchases, receipt files, returns, warranties, reminders and preferences.

Enforce user-level access controls on the server. Every user’s private data must be isolated from other users. Implement real create, read, update and delete operations.

Make all forms, buttons, navigation links, filters, charts and actions work. Include loading, empty, success and error states.

Do not remove or replace working features while building these additions. Do not use fake data to make unfinished features appear functional.

After implementation, test the main flows on mobile and desktop. Tell me which features are fully working, which need API keys or external services, and which remain incomplete. Do not claim a test passed unless you actually ran it.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.