How it works
Keep what matters. Remember what matters. Make it Critical only when it truly matters.
Save a note when you want to keep something. Create a reminder when you need it at the right time. Turn on Critical only when missing it really matters.
Two ways to start. One way to escalate.
Keep it without scheduling it.
A Note is for something you want to keep without deciding that it needs your attention at a specific time. Save the information now. If it becomes time-sensitive later, turn that same Note into a Reminder instead of starting over.
Keep it now. Remind yourself later if you need to.
Be reminded at the right time.
A Reminder is something you create directly when you need HISHI to bring something back to your attention at the right time. You do not need to create a Note first.
Set what matters, choose when you need it, and let HISHI handle the timing without turning every reminder into an urgent event.
Create the reminder when you need the reminder. Nothing has to come before it.
When missing it is not acceptable, turn on Critical.
Critical does not create a different kind of item. It strengthens the same Reminder so HISHI can give it a stronger path to your attention when it truly matters.
More visible
Designed to stand apart from ordinary reminder noise.
Harder to miss
Uses stronger reminder behavior where supported and appropriate.
Still under your control
You decide which Reminder deserves Critical mode.
Same reminder. Stronger attention.
Some reminders matter to more than one person.
A Reminder may be yours, or it may be something a family member, friend or colleague also needs to know about.
Shared doesn’t mean uncontrolled.
No connection? Keep going.
HISHI keeps supported Notes and Reminders usable on the current device even when the internet is unavailable. What you create stays local first; when connectivity returns, HISHI can synchronize it to the cloud.
No connection? Keep going. HISHI can sync later.
Your data should not depend on one phone.
Cross-device continuity begins only after the relevant data has synchronized successfully.
Synced first. Recoverable after.
No successful sync = no recovery on another device.
Simple on the surface. Serious underneath.
You should not need to think about synchronization queues, recovery logic or attention-routing rules. Those are system problems.