Fella, Kestirmeler'de otomasyon kurmanızı istemeden dikkat dağıtıcı uygulamaları engeller. Uygulamaları seçin, oturum veya rutin ayarlayın ve Ekran Süresi'nin halletmesine izin verin.
No. Fella's blocking flow does not depend on Apple Shortcuts. You do not need to create a personal automation, choose a trigger, assemble actions, or maintain a separate workflow in the Shortcuts app.
Everything needed for the block lives in Fella and Apple's Ekran Süresi system. Fella requests Ekran Süresi permission, opens Apple's app picker, stores your blocking configuration, and uses the system's Managed Settings and Device Activity frameworks to apply it.
Shortcuts remains available for everything else. Fella does not disable or replace Apple's automation app. Any unrelated Shortcuts you already use can remain separate from your app-blocking setup.
A custom automation asks you to design the workflow. You may need to decide which trigger starts it, which actions run, what happens at the end, and how to edit the sequence later. That flexibility is valuable when you want a custom system; it is overhead when you only want selected apps blocked.
The setup is split across interfaces. A blocking method built around Shortcuts can send you between an app, the Shortcuts editor, automation settings, and system permissions. Fella keeps app selection, session timing, routines, and emergency access inside one dedicated product flow.
Custom does not mean bad or universally unreliable. Shortcuts is a capable automation platform, and some people prefer building their own workflows. Fella is for the person who would rather configure the outcome than construct the automation.
Family Controls handles permission and app selection. Fella asks for individual Ekran Süresi authorization and presents Apple's Family Activity picker so you can choose the apps or categories you want to restrict.
Managed Settings applies the system shield. During an active session, Fella gives iOS the selected-app rule. When you try to open one of those apps, the iPhone shows Fella's shield rather than relying on a Shortcut to launch or close something.
Device Activity handles timing. Fella registers manual and recurring intervals with Apple's Device Activity system. Its monitor extension reconciles the active blocking sources when those intervals start and end.
| Step | What you do |
|---|---|
| 1 | Download and open Fella |
| 2 | Grant Apple's Ekran Süresi authorization |
| 3 | Choose distracting apps or categories in the system picker |
| 4 | Select a duration or create a recurring routine |
| 5 | Start blocking—without opening the Shortcuts app |
There is no hidden automation-building step. The current iOS project contains no App Intent, SiriKit, or Shortcuts action in the blocking path. The primary setup is app selection plus timing, all presented inside Fella.
You still approve Apple's required permission. A no-Shortcuts setup is not permissionless. iOS must authorize Family Controls before Fella can shield selected apps. See how Fella works from selection through automatic relocking.
Start the session inside Fella. Choose the duration and begin. Fella stores the session dates, registers the Device Activity interval, and applies the selected-app shield without calling a Shortcut.
Apple sets the minimum interval. Manual sessions start at 15 minutes because Device Activity rejects shorter monitoring intervals. Fella supports longer sessions for a work block, evening, full day, or weekend.
The block ends with the session. Fella reconciles its active blocking sources when the interval finishes, so an overlapping routine can remain active even when the manual session ends.
Routines repeat on the days and times you choose. Fella saves the routine and registers its schedule with Device Activity. Apple's system then runs Fella's monitor extension when the interval starts and ends.
No personal automation is required. You do not need a time-of-day Shortcut, separate start and stop actions, or an automation for every weekday. The routine itself contains the selected apps and recurring schedule.
Use the detailed guide for timing questions. See how to block apps at certain times on iPhone, including overnight and recurring schedules.
Every active session gets one five-minute acil kilit açma. Use it for a message, code, travel detail, or another task that cannot wait. Fella removes the shield temporarily and starts the fixed five-minute window.
The apps are blocked again automatically. Fella registers the emergency interval with Device Activity, and the monitor extension reapplies the current rule when the window ends. The main app also reconciles expired unlock state when it runs.
There is no Shortcut to trigger or reset. The allowance belongs to the current blocking session. It does not accumulate, and a second unlock is not available within that session. Read the exact acil kilit açma rules.
| Decision | Shortcuts-based approach | Fella's Ekran Süresi approach |
|---|---|---|
| Initial setup | Build or import an automation and configure its actions | Choose apps and timing inside Fella |
| Trigger model | Depends on the automation you create | Manual session or recurring Device Activity routine |
| Blocking mechanism | Depends on the app and Shortcut actions involved | Managed Settings applies Apple's system shield |
| Schedule editing | Edit the personal automation | Edit the routine inside Fella |
| Emergency access | Depends on the custom workflow | One fixed five-minute unlock per active session |
| Flexibility | Broad, general-purpose automation | Focused selected-app blocking |
| Best fit | People who want to build a custom workflow | People who want the blocker to own the workflow |
The difference is ownership of the setup. Shortcuts gives you building blocks. Fella gives you a purpose-built iPhone app blocker with selection, timing, shields, and controlled emergency access already connected.
Both approaches can be legitimate. A tailored Shortcut may be ideal if you enjoy automation and need unusual triggers. Fella is the cleaner choice when you want to choose apps, set the time, and move on.
Fella keeps the job narrow. It blocks selected distracting apps in manual or scheduled sessions, provides one controlled emergency window, and automatically restores the block. It is not a replacement for every feature in Shortcuts or Ekran Süresi.
Your useful tools stay yours. Shortcuts can continue running unrelated automations, and apps you do not select remain available. If Apple's built-in limits have not matched the behavior you want, compare Fella with the broader Ekran Süresi approach.
No. Fella's blocking flow has no Apple Shortcuts, App Intents, or Siri automation dependency. Selection, sessions, schedules, and acil kilit açma are handled inside Fella with Apple's Ekran Süresi frameworks.
Fella requests Ekran Süresi authorization, lets you choose apps with Apple's picker, applies shields with Managed Settings, and schedules intervals with Device Activity.
No. You configure manual sessions and recurring routines inside Fella. You do not need to create triggers or actions in the Shortcuts app.
Yes. Fella routines register recurring intervals with Apple's Device Activity system. Choose the days, times, and selected apps inside Fella.
Yes. Start a manual session inside Fella and choose how long it runs. Apple sets a 15-minute minimum for the Ekran Süresi monitoring interval.
No. Each active session includes one five-minute acil kilit açma. Fella temporarily removes the shield and automatically reapplies it when the five minutes end.
Not universally. Shortcuts is a flexible automation tool and may suit people who enjoy building custom workflows. Fella is for people who prefer a dedicated blocking interface.
Yes. Fella does not replace or disable the Shortcuts app. Existing automations can remain separate from Fella's Ekran Süresi blocking.
No. Fella uses Apple's Ekran Süresi frameworks for a focused job: selected-app blocking through manual or scheduled sessions with one controlled emergency unlock.
