Best Shortcut for iPhone 13 Pro: A Simple Menu

32 Min Read
32 Min Read
Silver-haired man in sculptural ivory fashion gestures toward an illustrated iPhone menu beside a direct-action versus menu comparison.
Choose a direct action for one job, or a small menu when choosing among several tasks is useful.

The best shortcut for an iPhone 13 Pro is the simplest one that removes a task you actually repeat; for several everyday choices, a small custom menu is a useful starting point. Use a built-in control when you only need one setting, and choose a menu only when having several actions behind one entrance makes the phone easier to use. Start with a harmless app-opening example, then keep it only if it improves your normal routine.

Which shortcut is worth keeping on your iPhone 13 Pro?

A useful shortcut has a clear beginning and an observable finish. “Open Maps” is a small, understandable job. “Make my phone better” is not: it could mean changing brightness, silencing interruptions, finding an app, or extending the time between charges. Those problems need different solutions, so a collection of impressive-looking downloads is a poor substitute for deciding what should happen when you tap.

For a first custom build, this guide recommends a manually launched Daily Menu with Maps, Music and Camera choices. That is an editorial recommendation for learning and organizing a few frequently used destinations, not a claim that this menu is universally fastest. If those three apps already sit together on your first Home Screen, a folder or the existing icons may be easier. A shortcut earns its place by removing friction, not by existing.

Think about the moment before you use it. Are you trying to adjust something immediately, repeat a preset result, or choose between several different jobs? That distinction matters more than the phone’s age or the number of actions in a downloaded routine. The same iPhone can benefit from a direct brightness control in one situation and a custom app menu in another, without either becoming the single best answer for everyone.

Illustrated phone and three cards compare a built-in control, one repeated shortcut task and a small menu, with the silver-haired presenter pointing.

Match the entrance to the need: one setting, one repeated task, or a choice among tasks.
Match the entrance to the job
Your actual needA sensible starting pointWhat would make it a poor fit
Adjust one setting nowUse the relevant built-in control.A custom menu adds a choice before a control you already know.
Repeat one specific resultUse a small shortcut with a clear name.The result changes every time and still needs substantial manual input.
Choose among a few destinationsTry a manually launched menu.Finding an item in the menu is harder than using your existing icons.
Run a task after an eventConsider an automation after the task works manually.The event is unpredictable, or an unwanted run would be disruptive.

On a narrow screen, swipe horizontally to compare.

Judge the whole route, not the first tap

A route includes finding the entrance, choosing an item, handling any prompt, and completing the task in the destination app. A menu might reduce Home Screen clutter while adding a selection step. That can be a fair trade for someone who values a consistent entrance, but it is not automatically a time saving. Compare the complete task against your current method under the same conditions, with the phone unlocked and the desired app available.

For example, imagine a person who keeps travel, listening and photography apps on different Home Screen pages. A menu gives those unrelated destinations one recognizable entrance. Now imagine someone who normally wants Camera and already reaches it immediately. Making that person open a menu first would solve a problem they do not have. These are illustrative situations, not measured user results or evidence from product testing.

Use labels that describe the result you will receive. A button called Maps should open Maps; a button called Start my journey would imply more, such as a destination and a route. Avoid ambitious names before adding the actions needed to support them. Precise naming makes a routine easier to understand later and makes troubleshooting less ambiguous when something opens but the expected activity does not begin.

This distinction also separates convenience from hardware performance. A menu can make an app easier to find; it does not upgrade the processor, expand storage or repair a component. The site’s guide to smartphone hardware and software explains that wider relationship. Here, the useful question is narrower: does the entrance take you to the right place with less effort in the situation that matters to you?

A fixed routine and a choice solve different problems

Imagine the same person uses Maps every weekday morning but Music only occasionally. Putting both behind a menu treats them as equal choices even though the common task is predictable. A direct Maps entrance can suit that repeated moment, while the menu remains useful for less predictable moments. You do not have to make one shortcut govern every situation, and an occasional exception does not justify adding more decisions to the most frequent route.

Now change the constraint: the person prefers one consistent entrance because locating small icons across multiple pages is difficult. The added menu choice may be worthwhile even when it involves another tap. That is an access decision, not a speed contest. Use familiar short words and a manageable number of items; do not depend on decorative icons alone to explain a destination. If building the menu is the obstacle, keeping ordinary app icons visible is a valid simpler alternative.

Keep your first version deliberately limited

For the example below, have Shortcuts, Maps, Music and Camera available on the phone, and work while stationary. Use the apps installed on your own device; the example does not require a music subscription, because its Music choice only opens the app. If an example app is unavailable, choose a different installed app and change both the label and its destination together. There is no reason to install an unfamiliar service just to copy a demonstration.

  • Use a built-in control for an occasional adjustment rather than building around a problem you rarely have.
  • Use a direct shortcut when you already know the single result you want.
  • Use the menu example when choosing among a few destinations is the useful part.
  • Leave messages, purchases, deletion and automatic triggers out of the first build.

The small scope makes mistakes easier to spot. If selecting Maps opens Music, there is one obvious mismatch to investigate. A much larger routine might also change settings, retrieve data and contact another service before you notice anything unusual. Simplicity is valuable here because it makes the behavior inspectable, not because a particular action count has been proven optimal.

How do you build a simple Daily Menu without unwanted actions?

Build one working app-opening action first, then create a separate menu with one destination under each choice. This separates two questions: whether the phone can perform the chosen action, and whether your menu routes to it correctly. Apple’s custom-shortcut instructions describe creating a shortcut, adding actions and running it to check the result. The action search and finishing controls can look different across iOS versions, so follow the action names rather than the exact position of an illustrated button.

First establish a one-action baseline

  1. Open Shortcuts and use + to create a new shortcut in the shortcuts collection.
  2. Search the action list for Open App and add that action.
  3. Tap the app parameter in the action and select Maps from your installed apps.
  4. Rename the shortcut Open Maps Check, finish editing, and run it while the phone is unlocked.
  5. Confirm that Maps opens. Do not expect a route to start; opening the app is the entire result of this baseline.

Three illustrated steps show creating a shortcut, setting Open App to Maps and running it once, beside the presenter using a phone.

Set the Open App parameter to Maps, then check that Maps opens before adding menu branches.

If Maps does not open, solve that basic issue before building branches. Check that the action names a real app rather than leaving its App parameter unset. Open Maps normally to confirm that it is available. An app showing its own welcome or permission screen is different from Shortcuts failing to launch it. Complete only the setup that you understand and want; do not approve unrelated access simply to make a test appear successful.

The baseline is intentionally disposable. It is a reference point for this build, not another permanent icon you must keep. Someone who finds the editor difficult can stop here and continue using an ordinary app icon instead. A one-action shortcut is useful only if its chosen launch method improves access; it does not make opening an already accessible app inherently better.

Create the choices before adding their destinations

  1. Create a new shortcut and name it Daily Menu.
  2. Add the Choose from Menu action. If a prompt field is available, use What would you like to open? as the question.
  3. Rename its initial choices Maps and Music, then add a third choice called Camera.
  4. Run this unfinished version only to inspect the choice labels, then return to editing. No app destination has been assigned yet.

Presenter taps a phone beside illustrated Daily Menu setup steps and a three-row menu labeled Maps, Music and Camera.

Create the choice labels first; destinations still need actions in their corresponding branches.

The choice names are the visible part of the menu, but they do not create the behavior. Think of them as labels on three doorways that still need destinations. A correctly spelled Camera item can do nothing if no action sits in its branch. Likewise, a convincing description in a shared shortcut tells you less than the actions actually placed beneath it. Keep that distinction in mind while connecting the next part.

There is no need for a nested menu in this example. A second level would introduce another decision before opening one of three apps. Nesting can be justified in a larger, clearly structured workflow, but it should answer a real organizational need. For a first build, flat choices make the relationship between the selection and the destination visible without requiring the reader to remember where an item was hidden.

Put each action inside its own branch

Add three Open App actions and set their app parameters to Maps, Music and Camera. Position Open Maps beneath the Maps marker and before the Music marker; position Open Music beneath Music and before Camera; put Open Camera beneath Camera and before End Menu. Touch and hold an action to move it if necessary. The important detail is the boundary around each branch, not the action card’s color or the space between cards.

Apple’s Choose from Menu explanation confirms that the selected option follows its corresponding pathway. For this design, keep the area after End Menu empty: it is outside the individual choices. Placing app-opening actions there would no longer express the intended one-choice, one-destination relationship. The illustration below shows the desired arrangement as a teaching diagram, rather than a screenshot of a particular iOS release.

Illustrated shortcut layout places Open Maps, Open Music and Open Camera inside their matching menu branches, with an empty area after End Menu.

Put each Open App action under its matching choice and keep the area after End Menu empty for this example.

Use a simple read-through before running it. Start at Maps and look down until the next choice marker: only its own destination belongs in that section. Do the same for Music and Camera. This is a visual boundary check within the editor, not a programming exam. If moving a card is awkward, rebuild that small branch slowly rather than adding more actions to compensate for a location you cannot identify confidently.

The completed menu should stop at opening the selected app. Opening Music does not select a track or guarantee playback. Opening Camera does not press the shutter, and opening Maps does not choose a destination. Those limits are useful in a starter example because the next consequential action remains visible in the app where you normally perform it. They also give the test in the next section a clear stopping point.

The app may open to content it was already displaying. For instance, Maps might show a place you viewed earlier, while Music might show a previous library screen. That does not necessarily mean the shortcut selected that content: this example contains no instruction to choose a place, song or album. Judge the destination first, then distinguish the app’s existing state from a result your shortcut explicitly requested. Avoid using a familiar screen as evidence that an unconfigured extra action happened.

Expand only when the new result deserves its own instruction

Suppose you later want the Music choice to play a particular playlist. That is a different task from opening the app: it introduces a content choice, possible account requirements and a playback result that needs checking. Treat that change as a new version of the routine. Do not rename the existing button Play my playlist while leaving its original Open App action unchanged, or assume that a menu label can configure the app for you.

Similarly, a brightness preset has a specific percentage and a recovery route; it deserves more instruction than a casual extra menu item. Follow the separate iPhone 13 Pro brightness-shortcut guide if that is the repeated job you actually need. Keeping its detailed setup there lets this page concentrate on choosing and validating a menu rather than repeating another tutorial’s entire procedure.

A good expansion changes something useful that you can describe in one sentence. “Add an installed app I use daily” is a clear organizational change. “Add every interesting action I find” has no stopping rule. Keep the menu small enough that each label remains easy to recognize. If you start reading the entire list every time, separate direct entrances may serve you better than further customization.

Where should you launch the menu, and how do you know it works?

Use the shortcut tile while building, then try one Home Screen entrance after the branches work. A visible entrance provides a straightforward comparison with your normal app icons. Adding several gestures and automatic triggers at once would make it harder to tell whether an unexpected result came from the menu, the trigger, or the destination app. Keep those layers separate until there is a reason to combine them.

Add one Home Screen entrance

  1. Open Daily Menu in the shortcut editor.
  2. Open the shortcut’s name menu or its Details/Share controls, depending on the iOS version, and find Add to Home Screen.
  3. Choose a short recognizable name, such as Daily Menu, and confirm Add.
  4. Return to the Home Screen, tap the new icon, and check that the Maps, Music and Camera choices appear.

Three illustrated steps show opening Daily Menu, finding Add to Home Screen and tapping the added icon to display Maps, Music and Camera choices.

After the branches work, add one visible entrance and confirm that it opens the intended menu.

Apple documents adding shortcuts to the Home Screen, although the editor control used to reach that option can vary. Do not confuse adding a shortcut entrance with bookmarking a website from a browser. The first runs your saved shortcut; the second opens a web destination. An icon alone does not reveal which behavior sits behind it, so check the result after adding it.

Place the entrance somewhere you can find without hunting. The useful comparison is with the arrangement you already use, not a deliberately inconvenient version of it. If Maps, Music and Camera are already easier to reach individually, keep that arrangement. If one menu replaces repeated searches across several pages, it may earn a place. Neither result requires a stopwatch, a written log or a claim about a universal number of seconds saved.

Alternative entrances are optional. Siri can run named shortcuts, and Back Tap is available on supported iPhones, including this generation. However, a spoken entrance or a tap gesture still has to fit the setting and the person using it. A visible menu may remain preferable when voice use is inconvenient or an unintentional trigger would interrupt another task. You do not need to assign a gesture to make the Daily Menu complete.

The iPhone 13 Pro does not have the dedicated Action button found on some newer models. Its side button should not be treated as a freely programmable replacement for that hardware. A tutorial showing Action-button assignment on another iPhone therefore does not automatically apply to this one. Model compatibility and iOS compatibility are separate checks: a software update cannot add a missing physical button.

Check each choice and the route that opens it

Use the following acceptance sequence while stationary, with the phone unlocked. These are checks to perform on your own device, not reported test results. Apple’s guidance on testing actions supports checking a sequence as it develops; the branch checks here are an editorial application to this specific three-app design. They help separate a routing mistake from an app’s own behavior.

  1. Run Daily Menu from its tile, choose Maps, and confirm that Maps opens.
  2. Return to Shortcuts, run it again, choose Music, and confirm that Music opens.
  3. Run it once more, choose Camera, and confirm that Camera opens without taking a photo.
  4. Run it again and dismiss the menu without choosing a destination. Check that no destination opens.
  5. Repeat those checks from the Home Screen entrance. If a result differs, compare which saved shortcut each entrance runs.

Illustrated acceptance checklist pairs each Daily Menu choice with its expected app and shows dismissal opening no app, with empty result boxes.

Check all three choices and dismissal from the shortcut tile, then repeat from the Home Screen entrance.
Use the visible result to locate the problem
What you seeWhat it suggestsNext useful check
A choice opens the wrong appIts label and destination do not match.Check that branch's Open App parameter and its position.
The selected app opens, then another appearsAn extra action may be running afterward.Inspect the selected branch and the area after End Menu.
The menu appears but nothing opens after a choiceThe branch may be empty or incomplete.Find that choice marker and its assigned action.
The app opens to a setup screenThe destination app is asking for its own setup.Read its request rather than changing the menu name.
The tile works but the Home Screen entrance differsThe two entrances may point to different shortcuts.Compare the shortcut names and rebuild the entrance if needed.

On a narrow screen, swipe horizontally to compare.

When investigating a mismatch, change one relevant detail and repeat the failed check. Moving several cards, changing names and adding a new launch method together can hide the cause of a fix. A small menu gives you an advantage: there are only a few destinations to compare, so you can make the intended relationship explicit instead of guessing whether a long routine is doing the right thing somewhere out of sight.

A successful launch is not a successful downstream task. Maps can open while a route still needs a destination; Music can open while playback remains paused. Judge the shortcut against the result it actually contains. If you need a richer outcome, define that separately and verify its extra steps. This prevents a common disappointment: describing a basic launcher as an automation and then expecting it to finish an activity it was never configured to perform.

Use the menu in the ordinary situation for which you built it, and decide whether it is worth keeping. The observable improvement might be fewer places to search, a clearer choice, or easier access for your own needs. It need not be a dramatic transformation. If the menu adds hesitation, simplify the labels, reduce the choices or return to direct app access. A discarded shortcut can still have taught you which entrance fits better.

Which shortcut downloads and promises should you avoid?

Avoid a shared shortcut you cannot explain well enough to understand its important actions, especially when it asks for unrelated data or sends information elsewhere. A familiar title is not a security guarantee, and a shortcut shared by a friend may contain steps neither of you intended. The three-app example above is deliberately built manually so its limited behavior can be inspected without trusting a downloadable routine.

Inspect behavior before approving access

  1. Open the shortcut’s action view before running an unfamiliar routine and read through the sequence, including branches.
  2. Compare requested information with the advertised job. A simple app launcher should not need a separate step to collect contacts or upload photos.
  3. Look for consequential operations such as sending content, deleting files, running scripts or contacting a web address; verify any destination and purpose before proceeding.
  4. Decline access or stop using the shortcut when you cannot account for a consequential step. Use a simpler manual alternative instead of granting access to see what happens.

Four illustrated checks show reading shortcut actions, matching data to the task, inspecting consequential steps and stopping when a step is unexplained.

Read the actions and compare requested data with the task before approving access to an unfamiliar shortcut.

The presence of a web action does not automatically prove malicious behavior. A weather routine might legitimately contact a service; a file-sharing routine might legitimately upload a selected file. The useful question is whether the action, destination and data match the promised task. Without understanding those details, you cannot infer safety from the creator’s chosen icon, the length of a description or a reassuring shortcut name.

Apple’s Shortcuts privacy guidance explains that data access can prompt for permission and that privately shared shortcuts require verification. If you already granted access, review the shortcut’s Details and Privacy controls; available options depend on what it has requested. Privacy settings help control access, but they are not a substitute for understanding what the routine does with information you allow it to use.

Do not enable advanced sharing or scripting options just because an old tutorial tells everyone to do so. A setting that exists for a particular workflow is not a universal setup requirement. The manually built Open App menu does not need an external script, a third-party shortcut collection or an instruction to disable protections. If a supposed equivalent asks for those changes, investigate the difference before assuming it is necessary.

A routine can also be inappropriate without being malicious. A shortcut written for someone else’s household might address the wrong person, use an account you do not have, or refer to a file location that means nothing on your phone. A successful import would not establish that those assumptions fit. For a beginner, a smaller routine whose purpose and dependencies are visible is easier to evaluate than a sophisticated workflow built around another person’s circumstances.

Separate convenience promises from hardware care

A “water eject” routine is not proof that a wet phone or connector is dry. Do not use a sound, animation or completion message as permission to reconnect a wet charging cable. Apple’s liquid-detection guidance warns against charging through a wet connector and gives the appropriate drying precautions. A shortcut result cannot inspect corrosion or certify that moisture has left the connector.

The same skepticism applies to battery claims. A convenient entrance to a power setting is different from restoring the battery’s physical condition. Avoid routines advertised as repairing battery health merely by running a software sequence. If that is the real concern, the site’s battery-health explanation separates everyday runtime from longer-term battery condition. Do not turn a menu-selection article into a reason to install a supposed hardware cure.

Finally, distinguish the phone model from features shown in a general Shortcuts guide. This iPhone can use ordinary manually assembled actions without gaining every feature offered on newer hardware. A feature requiring Apple Intelligence or a newer physical control is not unlocked by renaming a shortcut. When a shared routine depends on something absent from your device, choose a supported simpler version rather than expecting a missing action to repair itself.

Frequently asked questions

Do I need to buy an app to make this menu?

No paid companion app is required for the manual example. It uses Shortcuts and installed destination apps. Opening Music is separate from subscribing to a streaming service; the menu does not promise access to paid content.

Can I use this on an iPhone 13 Pro Max?

The same menu design can be built on an iPhone 13 Pro Max with the necessary apps and Shortcuts available. Follow the controls in your installed iOS version. A larger screen changes the display area, not the intended one-choice, one-destination behavior.

Does the menu work without an internet connection?

The menu and its app-opening steps do not include a network request of their own. The app you open may still need connectivity for its next task. Opening Maps is different from obtaining online directions, and opening Music is different from streaming a track.

Will this bypass the lock screen or app authentication?

No. Do not treat a shortcut as a way around device or app security. The instructions use an unlocked phone, and protected actions may require authentication. A shortcut name or Home Screen icon does not remove those requirements.

Is there a ready-made download for the example?

This guide teaches a manual build so you can inspect every choice and destination. It does not provide an installed or device-tested shortcut download. The instructional pictures show the intended arrangement; use the complete text instructions to build and check your own version.

Choose one entrance that earns its place

Begin with the repeated task you actually want to simplify. If the answer is one setting, use its direct control; if a few destinations belong behind one entrance, build the small menu and check each branch before adding convenience features. Keep the version whose behavior you understand and whose result is useful in normal use. That is a stronger reason to keep a shortcut than an impressive name or a long list of actions.

ExpertsGuys.com is an independent research-driven publication specializing in Artificial Intelligence, Consumer Health Insights, Home Living & Interior Tips, Food Knowledge & Practical Cooking Guides, Personal Finance & Investing, Technology Gadgets & Productivity Tools, and Everyday Lifestyle Optimization. We share news and updates, if you have any questions, you can email us!
Article link copied