Mobile app readiness
Review how the marketplace can behave like an installable mobile shopping app while keeping bids, saved searches, pickup reminders, seller messages, and support actions easy to reach.
Home Screen Install
- The demo includes a web app manifest so the storefront can be reviewed as an installable home-screen experience.
- Brand color, app name, icon references, display mode, and start URL stay aligned with the deployed marketplace package.
- Install prompts should stay optional and never block search, bidding, listing, or checkout review.
Saved Search Alerts
- Saved searches connect to fresh matches, price drops, ending auctions, category proof, and nearby pickup options.
- Mobile alerts should open directly to the matching search or item, not a generic landing screen.
- Quiet hours and alert priority should respect the user choices shown in notification preferences.
Bid and Offer Alerts
- Outbid, winning, reserve met, ending soon, offer countered, accepted offer, and auction won states need clear mobile actions.
- Urgent alerts should take the user to the item, bid review, offer review, or cart review with the current status visible.
- Lost bids should point to similar items and sold comps instead of dead ends.
Pickup Reminders
- Hub pickup reminders should show the item, hub, window, release state, QR status, and required documentation.
- Local pickup reminders should keep private handoff details protected and route support issues through the selected order.
- Missed pickup paths need reschedule, support, seller visibility, and no-show notes.
Offline-Safe Order View
- Order status, item snapshot, hub address, pickup window, QR readiness, and support reference should remain readable during a weak connection.
- The demo shows order timelines and report paths without pretending live offline storage is connected.
- Launch should define which order fields can be cached safely and when stale data must be refreshed.
Seller Mobile Actions
- Sellers need quick mobile access to offers, questions, listing quality fixes, hub intake windows, and order issues.
- Draft listing prompts should keep required photos, condition fields, shipping choices, and pickup options readable on a phone.
- Business seller approvals should remain clear when owners review changes from mobile.
Account Safety
- Mobile account actions should expose active sessions, verification state, notification choices, privacy controls, and report paths.
- Security alerts need plain language, support routing, and a safe way to review suspicious activity.
- Launch needs tested recovery paths before real accounts can depend on mobile-only access.
App Quality Review
- Owners should review install behavior, first-screen shopping density, mobile nav, alert routing, order fallback, and support paths together.
- Device review should cover phone sizes, tablets, keyboard access, screen readers, reduced motion, slow networks, and long item titles.
- Release approval should confirm no private account, payment, or support data is exposed through public cached pages.
Account Security
Trusted devices, mobile alerts, account safety, recovery readiness, and suspicious activity review.
Mobile Quality
Navigation, focus states, reduced motion, touch targets, contrast, and responsive stability.
Notification Preferences
Auction alerts, offer updates, order and pickup notices, quiet hours, and delivery review.
Saved Search
Fresh matches, price movement, demand signals, and alert-ready inventory.
Order Status
Timeline, pickup state, issue actions, item snapshot, and support reference.
Pickup Scheduler
Pickup windows, QR release, reminders, no-show handling, and support notes.
Account Preferences
Alerts, privacy choices, handoff settings, seller visibility, and account safety.
Current demo state
Mobile app behavior is represented.
The static demo includes manifest metadata, mobile navigation, saved searches, alerts, order timelines, pickup scheduling, and account preference routes without sending external messages or storing private device data.
Future platform state
Live mobile launch needs connected services.
A launched marketplace needs install testing, service worker rules, safe caching limits, verified alert channels, account recovery, device review, app monitoring, and support ownership before shoppers rely on it.