Sellavie.ai mobile: turning the dashboard into an operator surface
Adding an Expo mobile and tablet app across auth, dashboard, admin, products, conversations, settings, and training surfaces — and why mobile changes the product contract.
This phase changed Sellavie from a web dashboard into something closer to an operator tool.
The commit added an Expo mobile and tablet app with auth screens, admin screens, dashboard screens, conversations, orders, platforms, products, settings, training, shared UI components, API client code, navigation, theme constants, and app assets.
Why mobile mattered here
The users for a social sales tool are not always at a desk.
They check conversations when a message comes in. They review orders from their phone. They update product settings between meetings. If the product only exists comfortably on desktop, it is not matching the actual rhythm of the business it is serving.
What it changed about the system
Mobile expands the surface area in ways that are easy to underestimate.
Now auth, API contracts, loading states, navigation, admin privileges, and operational flows have to make sense outside the browser. Error handling that was acceptable on desktop becomes intolerable on mobile when network conditions are unreliable. State that could stay in memory on web has to survive navigation events on mobile.
That creates more work, but it also makes the system more honest about its own contracts. If an API response is too slow for mobile, it was probably too slow for web users too — mobile just makes the problem visible first.