Writing one line beats reading about it.
Five minutes without an account, seven days free after signing up.
There is no date field and no time field to fill in. Write one line the way you'd jot it down, and Noti splits out the date, time, place, and title on its own.
Most calendar apps ask for a title, a date, a start time, an end time, and a location — in that order, across two or three screens. Adding one appointment takes six or seven taps. The real problem is not the taps. It is that this whole ritual is slower than the moment you were trying to capture.
Natural language input inverts the order. Instead of you conforming to the form, the app reads your phrasing. "Team review next Tuesday at 3pm" becomes a dated, timed event with a title. What matters is not that typing got faster — it is that the hesitation disappears. When recording is cheap, you record more, and that is what actually determines whether a system survives.
When a line arrives, Noti looks for four things. You do not need all four — a single date cue is enough to produce an event.
Date phrasing falls into four families. Relative dates count from now ("today", "tomorrow", "the day after tomorrow"). Absolute dates name a calendar coordinate ("March 14", "2026-05-01"). Weekday forms count in weeks ("this Friday", "next Tuesday"). Interval forms count in gaps ("in 3 days", "in 2 weeks", "the 15th of next month").
All four are recognized, and so are common abbreviations. Bare numeric forms like "5/1" are picked up as dates too — though an unqualified string of digits can be misread, so writing the month name is safer when it matters.
Noti was built for Korean time expressions first, and that remains the deepest part of the engine. English expressions are supported as well. Each expression page shows what the live engine actually returns, not a hand-written example.
In everyday speech "let's meet at 7" almost always means the evening. Noti follows that convention: an hour with no am/pm marker resolves to the reading people actually use. If you mean the morning, adding one word ("7am", "morning") is enough to change it.
Fuzzy time bands like "around lunch" or "late tonight" resolve to a representative hour, and those results carry a lower confidence score. Anything with a low score is worth a glance before you save it.
Recognition runs in two stages. A rule-based engine scans the sentence first. It never touches the network, so results are instant, identical every time for the same input, and available offline.
Only when the rules find no date or time does it fall back to AI-assisted parsing — phrasing like "after the next meeting" that resists rules. That path needs a connection, and free plans have a usage limit on it.
Rules come first because the two things that matter most in event entry are speed and predictability. If the same sentence produces different results on different days, trust collapses. Common phrasing goes to rules; only the rare cases go to AI.
A line with no time cue does not become an event — it stays a note. That is deliberate. Turning every note into an event turns the calendar into a landfill.
When recognition is wrong, open the event and fix it, or use the undo that appears briefly right after creation. Recurring phrasing ("every Tuesday") is recognized; complex exception rules ("every other Tuesday except holidays") are not.
If you want to see it work before signing up, the free text-to-calendar tool takes a sentence and hands back an .ics file.
Five minutes without an account, seven days free after signing up.
Write it the way you’d text it — the date, time, and place sort themselves out.