Build multi-page LINE Rich Menus with aliases and tab switching

Components of a multi-page menu

Each page is a separate Rich Menu with its own image, areas, and ID. Create a richMenuAliasId for each destination, then assign richmenuswitch actions to the tab areas.

• Page A and Page B must be created with images
• Aliases and menus must belong to the same channel
• Alias IDs use a-z, 0-9, underscore, and hyphen, up to 32 characters
• Each switch action requires richMenuAliasId and data

A maintainable alias model

When a new products design is ready, create richmenu-DDD and update menu-products to point to it. Other pages keep using the same alias and do not need to be recreated.

Home page      alias: menu-home     -> richmenu-AAA
Products page  alias: menu-products -> richmenu-BBB
Services page  alias: menu-service  -> richmenu-CCC

Common implementation failures

Keep tab placement and order consistent across pages with a clear active state. Do not shrink tap targets merely to fit more tabs.

• Creating an alias before the target image is uploaded
• Pointing to a menu in another channel
• Moving tabs between images and confusing users
• Deleting an alias that is still referenced
• Testing only API responses instead of tapping on LINE mobile

A reversible release plan

Create all pages and aliases without changing the default. Test switching with a test user, then set the home page as default. Retain the previous mapping so aliases can be reverted quickly.