Use the existing catalogue route before commissioning an app to find a product family

A fictional distributor asks for a mobile app because repeat buyers cannot quickly find a small group of replacement parts. Before adding an installation and release process, the team observes the actual task on a phone.

Establish what the buyer needs

The buyer needs the current public information for product family F-18 and a way to request a quotation retaining the selected item. They do not need camera capture, a private account or offline editing. Those capabilities are not part of the observed problem.

The current website already supports a stable category route and filtered product list. The difficulty is navigation: F-18 is buried under a generic menu and its descriptive heading uses an internal warehouse term customers do not recognize.

Select a smaller change

The business approves a customer-facing heading and a prominent link to the existing F-18 category. It retains the supported web quotation path. The chosen scope changes discovery and wording, rather than duplicating the catalogue in another application.

In the preview, a representative test reader follows the new navigation on a phone, identifies item P-181 and sends a fictional quotation request. Staff receive the correct item reference. A saved browser bookmark opens the same current category route without creating a separate catalogue snapshot.

The editor then updates an approved test description for P-181 and reloads that route. The current wording appears through the same web publishing process. Product family F-19, its navigation and request references stay unchanged.

State the trigger for a different decision

The app proposal is deferred because the inspected website capability satisfies this task. The organization can reconsider if a later approved job requires device-specific evidence capture or managed offline work that the existing web arrangement cannot support adequately.

That future requirement would need its own device, storage, synchronization and maintenance review. Frequent mobile use alone does not prove installation is necessary.

Mobile application scoping can evaluate that later case. For the present one, website design provides a smaller correction with a clear result and one authoritative catalogue.