This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Oxslate: Someone Remembers
Someone keeps the list. You just get the reminder.
Other household apps are symmetric: two people log chores and get measured. OxSlate is lopsided on purpose. One person keeps the admin (bills, renewals, forms). The other gets one calm reminder at a time with a Done button, and needs no account, no email, no list. They can pause, decline, hand an item back or disconnect, and the sender can't override it. No streaks, scores or read receipts; the data model can't hold them. Hold to talk for 30 seconds and get separate, dated reminders.
In most households, one person ends up holding the admin: the renewals, the bills, the forms, the appointments. Nobody assigned them the job. They noticed first, and after a while the noticing became the job. The usual fix is a shared to-do app, but that just gives the other person a list to manage, and managing the list is often the hard part.
So OxSlate is lopsided on purpose. The person who keeps the admin gets the board, the queue and the account. The other person gets one calm reminder at a time, at a sensible hour, with a Done button. They never make an account, never see a list and never see a price.
The idea changed as I built it. I started with "no streaks, no scores" as the hook. Then my research turned up couples apps already saying the same thing, so that alone wasn't enough. What nobody had built was the receiving side as a space with its own rights. The recipient can pause, decline one thing, hand it back, take it over, have it read aloud, or disconnect for good, and the sender can't change any of that. Those rules live in the code itself, not in a settings screen. Repeat reminders have hard limits so the app can't be set up to nag. And the app never records whether a reminder was opened, so there's no number anyone could be shown.
I'd love your feedback, especially if you're the one who carries the admin in your house. Or the one who gets reminded.
About Oxslate: Someone Remembers on Product Hunt
“Someone keeps the list. You just get the reminder.”
Oxslate: Someone Remembers was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #75 on the daily leaderboard. Other household apps are symmetric: two people log chores and get measured. OxSlate is lopsided on purpose. One person keeps the admin (bills, renewals, forms). The other gets one calm reminder at a time with a Done button, and needs no account, no email, no list. They can pause, decline, hand an item back or disconnect, and the sender can't override it. No streaks, scores or read receipts; the data model can't hold them. Hold to talk for 30 seconds and get separate, dated reminders.
On the analytics side, Oxslate: Someone Remembers competes within Android — topics that collectively have 57.7k followers on Product Hunt. The dashboard above tracks how Oxslate: Someone Remembers performed against the three products that launched closest to it on the same day.
Who hunted Oxslate: Someone Remembers?
Oxslate: Someone Remembers was hunted by Faizan Ahmad. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Oxslate: Someone Remembers including community comment highlights and product details, visit the product overview.
Faizan Ahmad