Action Required App Bridge

On mobile, ActionBar removed
TitleBar 's primary action becomes an icon button

On the mobile view of embedded apps, the bottom "icon + text" bar (ActionBar) is going away. The primary action moves to an icon button at the top-right of the header, and secondary actions move into the overflow menu. If no icon is specified, + is shown by default.

On this page
  1. 30-second overview: What's changing
  2. Diagram: Mobile Before / After
  3. Details of the change (3 points)
  4. Scope and effective date
  5. Migration steps
  6. 5 key points for engineers
  7. 3 use cases you can apply to your work
  8. One-line summary for proposals

130-second overview: What's changing

On mobile embedded apps,TitleBar defined in primary action changes where it appears.
What used to appear in the "icon + text" bar at the bottom of the screen now becomesan icon-only button inside the title bar. Secondary actions are consolidated intothe overflow menu.

Before (mobile)

The primary action was shown in the bottom bar with "icon + text". Secondary actions also appeared on screen.

After (mobile)

The primary action becomesan icon-only buttonat the top-right of the header. Secondary actions are tucked into the overflow menu for a more consistent UI.

2Diagram: Mobile Before / After

Before: ActionBar (bottom bar) App screen primary action = icon + text 4/15 After: Icon button in the title bar App screen primary = icon only / secondary = consolidated into ⋯
What's changing is the mobile rendering (appearance and placement).TitleBar . The API itself for defining primary / secondary actions on continues to be used. The article does not mentionNot specified.

3Details of the changes (3 items)

Change 1

primary action → header icon button

Instead of the previous "icon + text bottom bar," it now appears within the mobile header asan icon-only button.

Change 2

secondary actions → overflow menu

secondary actions are consolidated into the overflow menu, improving consistency of the mobile UI.

Change 3

If icon is not specified, + is the default

If you do not pass an icon property to primary action, the + (plus) iconis used automatically.

4Scope of impact and effective date

ItemDetails
Affected apps TitleBar defines primary action or secondary actions onAll embedded apps that
Effective date April 15, 2026 Applied to all target apps at once
Whether action is required If the default + icon is fine,no action is required
If you want to show an appropriate icon, icon you must specify it explicitly
Target platform Mobile (the focus of the article). Impact on desktop isnot specified

5Steps to take

1

Check your TitleBar definitions

Audit whether your app defines primary/secondary actions on TitleBar .

2

+ is sufficient

If the default plus icon fits the context, no further action is needed.

3

icon explicitly

If you want to show an icon that fits the context, set icon property on the primary action.

What the article explicitly requires is "pass icon to the primary action"— that's the only point. This ensures the most contextually appropriate icon is displayed on mobile.

65 key points engineers should know

REMOVED

1. The mobile ActionBar is going away

The bottom "icon + text" bar UI is being removed on mobile. Revisit any layouts that assume a bottom bar.

2. Unspecified icon falls back to + fallback

Even for actions where a plus is inappropriate, such as "Save" or "Publish", a plus icon will appear if no icon is specified. Beware the risk of unintended icons being misread.

3. Secondary actions move one level deeper (overflow)

Secondary actions are placed inside . Since this adds one extra tap, reconsider the user flow if you've been placing frequently-used actions as secondary.

4/15

4. Applied automatically to all affected apps at once

Rolls out to everyone on April 15, 2026 with no opt-in. The release cannot be stopped, so finish reviewing your icon specifications before the rollout date.

5. Text labels disappear = icon self-explanatory power matters

On mobile, buttons becomeicon-only, and the previously visible text will no longer be shown. Verify on a real device whether the action's meaning is conveyed by the icon alone (including from accessibility and mis-tap perspectives). Since the article includesno specificssuch as API names or code examples, check the latest App Bridge / TitleBar documentation for implementation details.

73 use cases you can apply to your work

USE CASE 1

Get your in-house or client embedded apps through the rollout without incident

Problem
An embedded app in production has a primary action on TitleBar , but icon is not explicitly specified in some places, so on and after 4/15 an unintended + may appear on mobile.
Action
Audit all of your app's TitleBar definitions and explicitly specify a contextually appropriate icon on the primary action. For screens that rely heavily on secondary actions, also verify the flow after they move to overflow.
Impact
Prevents UI breakage, user confusion, and support inquiries after the rollout date.
Technical note
The change affects mobile rendering only. Desktop impact is not mentioned, so verify before/after on a real (mobile) device.
USE CASE 2

Mobile flow audit and rethinking the "action priority" design

Challenge
Multiple important operations were placed in secondary actions, but moving them into an overflow menu hides them one tap deeper, raising concerns about declining usage.
Approach
Reorganize actions into "one most important = primary" and "everything else = secondary." Promote the top action to primary so it stays visible in the header.
Impact
Reachability of key operations on mobile improves, helping maintain and increase completion rates.
Technical notes
Since primary is limited to one, prioritize icon recognizability above all. Also revisit the order and wording of items inside the overflow.
USE CASE 3

Standardizing icon + accessibility guidelines internally

Challenge
Because text disappears and only the icon remains, apps choose different icons inconsistently, making meaning harder to convey.
Approach
Establish an internal guideline mapping operations to icons (e.g., save = check, add = +, edit = pencil) and require icon to be specified across all projects.
Impact
UI quality of deliverables becomes consistent, reducing user learning cost and support inquiries.
Technical notes
When icon is not specified, + Treat the fallback as a sign of a design oversight, and adding it as a review checklist item makes detection easier.

8One-line summary you can use in proposals

"Starting April 15, 2026, on mobile for embedded apps, the primary action of TitleBar becomesan icon button in the header, and secondary actions move to the overflow.
If icon is not specified, + will appear, so before the effective date, take the small step of 'explicitly specifying an appropriate icon for the primary action.'"