NOTYFI / BUILDSnowYour build is ready.
All checks passed. Preview it whenever you’re ready.
JUST AN UPDATE. RIGHT WHEN IT MATTERS. A DIRECT LINE TO WHAT MATTERS
Less noise.
More signal.
Push notifications from your scripts, tools, and agents.
One phone app. No app to build.
◒ Built for iPhone / In active development
Your communities
Your tools
Your agents
Your everyday
NOTYFInowA lot more living.
The right signal. Right here.
START HERE / THE SIMPLE UTILITY
Send a push.
Send a push.
Skip building an app.
Something happens. Your phone knows.
A job finishes on your computer. A sensor changes at home. An agent needs your answer. Send a message to a topic path, and Notyfi brings it to your phone. You don’t need to build, host, and maintain a separate mobile app just to get that update.
- 01 Follow a topic path.
- 02 Send it a message.
- 03 Get the notification.
Start with a simple notification. Keep the context in the same place, and add a reply, a conversation, or a human decision when you need one.
Inspired by ntfy’s simple publish-and-subscribe model ↗.
THE ORIGINAL UTILITYLOCAL PREVIEW
⌁Your script→/builds→◒Your phone
YOUR NOTYFI INBOX
NOTYFI / BUILDSnow
↘
Your next useful update
lands here.
NOTYFI / BUILDSnowIllustration only · Nothing is sent to your phone
One request from a script
curl -d 'Build ready. All checks passed.' \
https://your-server.example/buildsUse your Notyfi server and topic path. Protected topics also need a publisher token.
Working core · iPhone app in active development · A free entry point is intended; included features, hosted plans, and usage limits are still being defined
01 / A CALMER WAY TO CONNECT
Life has enough tabs open.
Checking dashboards. Chasing updates. Switching apps.
There’s a better way to stay in the loop.
◎ Communities
⌁ Tools & automations
⌘ AI agents
◷ Everyday life
One inbox.All your signals.Choose what reaches you.
Connect tools and publishers that know when something changes. Keep the useful updates together, with the context to respond.
Keep the context. Lose the detour.
A focused thread holds the update, the details, and the conversation. Pick up right where the signal starts.
Do something with it.
Reply, approve, snooze, or set a reminder. Your answer flows back to the tool that asked.
02 / THE SIGNALS YOU NEED. ON YOUR TERMS.Your signals.
NOTIFICATION CONTROLS · PLANNEDYour signals.
Your way.
Choose what deserves your attention—and how it reaches you.
The direction is simple: connect the sources you care about, decide which changes matter, and shape the notification around your life. An agent’s question, a finished job, and a community update don’t all need to make the same noise.
01 The source you choose.02 The event that matters.03 The delivery that fits.
Today: replies, snoozes, and reminders. Planned: finer controls for source rules, sounds, quiet hours, and digests. This preview changes an illustration only.
A SIGNAL RULE / YOUR CHOICEINTERACTIVE CONCEPT
CHOSEN SOURCE→YOUR RULE→YOUR INBOX
NOTYFIPUSH + SOUNDTonight’s game moved to Field 3.
Coach Sam · First pitch is still 5:30 PM. Head to the north entrance.
A last-minute field change → push with sound → when it happens.
Illustration only · Device permissions and Focus settings still apply
03 / FROM SIGNAL TO SOMETHING DONEA signal.
A signal.
A conversation.
Your choice.
Just an update, a back-and-forth, or a whole group thinking together. Choose who can speak, who can reply, and who sees the conversation.
INTERACTIVE PRODUCT CONCEPT
9:41▮▮ ◓ ▰
notyfi.Your signalsAll caught up feels good.
Needs you 1All activity
FOR YOUR ATTENTION
Your print is ready.
The enclosure for your weekend project just finished printing. No need to keep checking the workshop.
That’s your signal.The rest of your day is yours.
▤Inbox⌁Topics⚙Settings
Try an action. See the conversation move forward.
Illustrative demo · No live notifications or external actions
ONE PATH / DIFFERENT WAYS TO CONNECTThe signal is the start.
The signal is the start.
You choose what follows.
A person, an agent, a team, or a group for the weekend. The use case doesn’t decide the conversation. The permissions do.
/projects/workshop
A useful update. Nothing to answer.
A script posts to its subscribers. Reading is enough; replies are turned off in this example.
WHO SEES IT · TOPIC SUBSCRIBERSShowing a one-way update to topic subscribers.
Conversation styles are independent of a channel’s lifetime. Members choose their notification preferences; posting and reply permissions determine who can participate and see messages. Group discussions and configurable channel permissions are planned. Local illustration only.
04 / ONE IDEA. MANY POSSIBILITIES.Your world.
Your world.
Your kind of signal.
For the people, projects, and everyday things
you choose to stay connected to.
YOUR COMMUNITIESPLANNED
Your people.
A clearer way to connect.
Teams, clubs, and communities can share updates, take private replies, or open a group conversation—with clear permissions.
Explore community updates ↓YOUR TOOLS & AUTOMATIONSWORKING CORE
Keep your projects moving.
Step away from the screen.
A home server, a job runner, or a workshop automation can send useful context when something changes.
YOUR AGENTSWORKING CORE
Let your agents work.
Keep approval in your hands.
Give an agent a direct line when it needs your approval. Review the request, make the decision, or add context—all in one conversation.
See the stronger approval direction →YOUR EVERYDAYPLANNED
Stay close to life.
Keep your attention.
A local event, a changing plan, or a group for the weekend. The vision is one place for the parts of life you choose to follow.
Explore temporary connections ↓05 / A DIRECT LINE TO YOUR TEAMEveryone gets the update.
GROUPS · PLANNEDEveryone gets the update.
The right people get the reply.
A rain delay. A new field. The bus leaving ten minutes early. Get the details to every subscribed family, with a private way to ask a question.
A few voices. A clear channel.
Only designated broadcasters—like the coach, team manager, or league organizer—can send updates to the topic’s subscribers.
A reply with the right audience.
Parents can message back to the admins. Organizers see it; other subscribers don’t receive it or get pulled into the conversation.
Built around your community.
A public league channel or an invite-only team group. Locations, schedules, last-minute changes, and follow-up questions in one place.
NORTHSIDE SOCCER / U14ILLUSTRATIVE CONCEPT
◎COACH + MANAGERBROADCAST →PPPALL SUBSCRIBERS
↗ COACH SAMEVERY SUBSCRIBER
Practice has a new home today.
Field 3, Northside Park · 5:30 PM.
Same team. See you there.
YOUR REPLYYOU + ORGANIZERS ONLY
Is the north entrance open for pickup?
Demo only · Nothing is sent
The team hears the update. The organizers handle the follow-up.
06 / HERE FOR THE MOMENTGood things
EPHEMERAL MESSAGING · PLANNEDGood things
don’t need forever.
ONE NIGHT / ONE CHANNEL LIVE CONCEPT
◷
Saturday under the lights
Volunteer crew · Invite-only · Illustrative event
01GATHER02COORDINATE03EXPIRE
✓
That’s a wrap.
This demo channel has expired.
Posting has closed and the example message is gone.
Interactive concept · No real messages or timer
A group with a purpose. A conversation with an end.
Bring people together for the time they actually need to be connected. The plan: temporary channels and messages with a defined lifetime. Share one-way updates, reply privately, or talk as a group—then let the channel close when its purpose is done.
Tournament weekend
Field changes, carpools, and pickup details. A channel for the weekend’s families and organizers.
The event crew
Volunteers, pop-up markets, and race-day staff. One broadcast line while the event is happening.
A short-lived shared plan
A group trip, a meetup, or a moving-day crew. Keep the useful updates close for the moment.
Planned product direction: automatic channel and message expiry. Retention and deletion rules are still being designed; this preview demonstrates the experience.
THREE CLOCKS. THREE DIFFERENT PROMISES.
Temporary coordination needs clear endings.
Posting closes.
Joining, broadcasting, and replies stop at the channel’s deadline.
Access expires.
Messages and actions become unavailable at their declared expiry.
Stored copies follow policy.
Primary storage, backups, and essential records need explicit deletion rules.
Conceptual lifetimes, not a time scale · Retention design is in progress · Recipient copies cannot be recalled
07 / YOUR AGENTS. YOUR AUTHORITY.Approve the action.
AUTHORIZATION · IN THE LABApprove the action.
Keep the human.
A useful agent knows when to ask.
We’re exploring a stronger kind of approval: review a specific action on your phone, confirm it with a registered credential, and have a protected executor check that permission before it acts.
The details you’re actually approving.
The exact content, destination, and deadline. If those change, the action needs a new approval.
A key can be part of your policy.
Physical FIDO2 security keys—including supported NFC keys—are part of the research. A key-based approval would be bound to one request.
Permission checked where work happens.
The protected tool checks the approved action and returns an execution result to the conversation.
Local prototype work, separate from today’s app. Hardware compatibility and the security design still need validation. This illustration does not use a real authenticator.
08 / A DIRECT LINE TO A GOOD MOMENTTwenty invitations.
LIMITED DROPS · PLANNEDTwenty invitations.
A moment to act.
THE AFTER HOURS / LIVE AT THE MUSEUMILLUSTRATIVE EVENT
VENUE → OPTED-IN FOLLOWERS
Tonight has an opening.
20 free guest-list passes. One per eligible member.
Announce→Claim→Confirm→Check in
0 claimed20 available
Local illustration · No tickets are offered or issued
Follow the places and people you care about. Be there when something opens.
A museum’s after-hours event. An artist’s surprise set. A venue’s returned seats. The vision is a chosen channel that leads to a useful action.
The channel lasts. The offer has a window.
Keep following the venue. Each drop has its own capacity, eligibility, and deadline.
A claim needs an authoritative answer.
Native drops would allocate inventory in server-accepted valid-claim order, with one entitlement per eligible member.
A retry shouldn’t take another pass.
The same claim returns the same result. Confirmation and check-in are separate steps.
Planned direction. Push arrival times can differ. The first venue pilots would link to an existing registration system before Notyfi manages inventory.
09 / WHAT WE’RE BUILDINGOne idea.
One idea.
Room to grow.
Your tools can reach you.
You can answer.
Notyfi starts with a simple utility: send a message from a tool, automation, or script to your phone without building a mobile app. The working core adds a focused iPhone inbox, replies, decisions, snoozes, and reminders.
Keep a whole group
in the loop.
Public and private channels with configurable posting and reply permissions: broadcasts, private replies, shared discussions, and temporary groups with explicit lifetimes.
A common place
for the things that need you.
Across your tools, people, and connected world: receive the signal, understand the context, and act. Stronger human authorization for agent actions is part of the research.
iOS first · Active development · Concepts on this page are labeled by status
10 / LESS SCROLLING. MORE PLAYING.
Leave a little signal.
Part reversible sequins. Part magnetic drawing board.
Absolutely no productivity required.
N / FIELD 001MAKE YOUR MARK ↗
A little touch goes a long way.Click + drag. Or use your finger. Undo a stroke anytime.
Your phone should
give you your life back.
We’re building Notyfi for the moments that matter.
Have a signal in mind? Let’s give it a shape.