AR support depends on the guest’s device, browser, permissions, operating system, and the quality of the model asset. A restaurant cannot assume that every person scanning a code will have the same capabilities. That makes a fallback essential for a reliable menu rather than an optional edge-case feature.
The fallback begins with the dish itself. Show a useful image, name, price, description, ingredients, availability, and dietary or allergen information independently from the AR action. If a guest never taps the enhanced feature, they should still receive a complete menu experience and be able to make a decision.
Camera access should be requested only after a guest chooses to try AR. Asking for permission on page load creates uncertainty and can make the menu feel invasive. Explain the action with simple language, provide a normal 3D or image route, and respond respectfully when permission is denied.
Model processing also needs a guest-facing fallback. A dish can be published while its model is queued or processing. In that state, show the food image and explain that the enhanced preview is being prepared without making the item seem broken. If processing fails, keep the dish useful and avoid exposing technical error codes to guests.
A normal 3D viewer is a valuable middle layer between a static image and AR. It can let guests inspect shape and presentation in the browser without needing camera permissions. It should still be lightweight, controllable, and optional. Do not autoplay rotation or make a guest wait for the viewer before showing the description.
Good fallback copy is honest and calm. “The image and dish details remain available on this device” is better than a vague “Something went wrong.” If a model is a mock or approximate visual, label it accordingly. Trust is more important than making the enhancement appear more advanced than it is.
Test unsupported paths deliberately. Use an older phone, deny camera permission, disable network temporarily, open the menu in a desktop browser, and try a failed model. The standard menu should remain navigable in every case. An enhanced feature is successful when it adds value for supported guests without creating a dead end for everyone else.