Why Unity for a shopping app
A game engine will carry a consumer application when the interface wants motion and depth that a standard mobile toolkit makes expensive. It will also fight you, unless somebody on the team knows where the edges are.
The edges are specific: store review, application size, battery, and the fact that a game engine has opinions about the keyboard, text input and accessibility that a shopping flow cannot ignore.
What we built
- A Unity mobile client for browsing and shopping, with the motion the founder wanted. FrugaList was a friend's shopping product, and we built all of it.
- A Django web service behind it for the catalog, the users and the transactions.
- A finished, working build.
The founder later shut the backend servers down over hosting costs, which is a product outcome and not an engineering one. We report it that way because a portfolio where nothing ever ends is not believable.
Why it matters to a buyer
It is the reason Unity sits in the mobile column of our stack and not only in the training column. Unity is also the engine behind SPARC, our immersive training platform.
- Unity
- C#
- Django
- Python
- iOS
- Android
What we can start on
A Unity build that has to behave like an application rather than a game. Or a consumer front end with real motion, backed by a service that holds up.