You do not need to put your phone in another room, make everyone stack their devices in a pile, or pretend nothing urgent could happen during dinner.
You need a boundary that makes reflex apps less available for one meal while keeping the people and tools you might genuinely need within reach.
That is a different problem from “use your phone less.” It has a start, an end, and a reason for the exception list.
Make dinner the boundary, not the whole evening
A vague rule such as “no phone at dinner” tends to create small arguments with yourself. Does it start when you begin cooking? When food reaches the table? What about a message from a child, a parent, a roommate, or someone you are waiting to hear from?
Give the rule a shape before you try to enforce it.
A useful first version could be: “From when we sit down until we clear the plates, social feeds and video apps can wait. Calls and messages from the people I need to hear from stay available.”
That is enough. It does not need to become a statement about phone habits, manners, or personal virtue. You are deciding what gets your attention during one shared part of the day.
Pick a version that fits how dinner actually happens in your home. Maybe it is a weeknight meal. Maybe it is one long Sunday dinner. Maybe it is only the twenty minutes when you tend to open an app while someone is telling you about their day.
The smaller and more concrete the moment is, the easier it is to notice whether the boundary fits.
Keep essential access separate from convenient access
This is where most dinner rules go wrong. They either block too much and feel unreasonable, or leave everything available “just in case.” Neither version tells you what to do when your hand reaches for the phone.
Start by separating essential access from convenient access.
Essential access might include calls, a message thread you are expecting, a delivery update, a transit app for someone coming home, or a timer you are using in the kitchen. Convenient access is the social feed, news app, short-video app, game, or browser habit you reach for because there is a quiet second at the table.
Apple’s current Screen Time guidance supports that distinction. It lets you set a Screen Time Schedule (called Downtime in iOS 26), set Time Allowances for app use, and choose apps and contacts that remain available regardless of your schedule or allowances. Apple also documents different schedules for different days of the week. Its Screen Time schedule guide is the place to check the current settings before you set up a native rule.
You do not have to explain every exception perfectly. Start with the things that would make the boundary feel unsafe or impractical if they disappeared. Everything else can wait until the meal ends.
Choose the apps that pull you away, not every app you own
A dinner boundary does not need an impressive blocked-app list. In fact, the dramatic version usually creates an excuse to abandon it.
Think about the first app you open when conversation pauses for a moment. Then the second. For many people, that is a social feed and a video app. It might be a news app that turns a quick headline into ten minutes of reading. The answer is personal, but the question stays useful: which apps turn a small gap in the meal into somewhere else?
If you need help making that distinction, choose the reflex apps that belong outside the meal before you set the boundary. The aim is not to make your phone useless. It is to keep a few familiar detours from deciding how dinner goes.
Leave messaging available only when it serves a real need during that window. “I might want to check” is not the same as “I need to be reachable.” You can revise the list later if the first version misses something important.
Pick the amount of friction on purpose
Sometimes a quiet reminder is enough. You see it, remember the meal you meant to have, and put the phone down.
Sometimes that does not interrupt the reflex. In iOS 26, Apple documented a stronger native option called Block at Downtime for the scheduled window. With it turned on, restricted apps cannot be opened during the scheduled window. With it off, Screen Time can show a reminder and let you continue using the app.
Neither setting makes you more serious. They answer different questions.
Use the lighter version if you are testing a new dinner boundary or if the timing changes often. Consider stronger friction only for a short, stable window where you have already decided what must stay available. Do not turn one distracting app at dinner into a reason to make every evening feel locked down.
Let the boundary repeat only when it earns a place
A dinner rule does not have to run every night. Test it on the meals that matter most first. Notice whether the start time is right, whether the app list is too broad, and whether an exception needs to be made explicit.
If it fits a regular weeknight rhythm, make that dinner boundary repeat on the nights it actually belongs. Calma’s focus routines are the useful next stop when the question becomes how to make a small moment-specific rule recur without rebuilding it each time.
Keep the product description plain. Connect Calma to Screen Time and choose the apps you want to restrict. You can create recurring focus rules for the days and times that matter to you, or start a temporary focus session and block your selected apps.
That is not a promise that your phone will become impossible to use. It is a way to make the choice visible before a reflex app gets the first say.
Adjust the rule after a real meal
Do not judge the boundary before you have used it at least once.
Maybe you kept reaching for an app that was not on the list. Maybe a message really did need your attention. Maybe the meal began later than the rule. Those are not failures. They are details your first version could not know.
Change one thing at a time. Shorten the window. Remove an app that does not matter. Add one essential contact path. Then try the next meal.
The goal is modest: let dinner belong to dinner a little more often, while the rest of your phone remains there when you need it.