Search uses the API instead of filtering only loaded products. A 400 ms debounce limits requests, and a request version check keeps older responses from replacing current results.
02 / RESILIENCE
A hiccup isn’t the end.
Products load in pages of 20. If another page fails, existing products stay visible with a retry action. Loading, empty, error, and success states give each request a clear outcome.
03 / DETAILS
Keep the flow going.
Pull-to-refresh reloads the active search. Images include placeholders and error fallbacks, and product details have a swipeable gallery with page indicators.
04 / STRUCTURE
Give data its own space.
A product model handles JSON conversion and a service handles HTTP requests. The interface uses StatefulWidget and setState for the catalog, and FutureBuilder for details.
03 / Validation & scope
A small app. An honest scope.
This technical assessment uses sample data and has no checkout or payment features. The repository includes one model unit test for numeric conversion and product title preservation; API requests and widgets do not have automated coverage.
The README records manual Android checks for browsing, search, retry, detail navigation, and refresh. It also documents AI assistance with guidance, review, and selected code edits.