Reward 360

Reward 360, known in the working files as "One App," is a loyalty programme turned into a shopping and travel destination. Rather than bolting a rewards catalogue onto a bank or a retailer, the product puts the loyalty wallet at the centre and builds an entire commerce ecosystem around it, so earning and spending points happens continuously through things people already do: booking a flight, reserving a hotel, buying cinema tickets, shopping for a phone, or topping up a mobile.

The architecture runs Home into Digital commerce into Extended store, branching into three families. **Book** covers six travel verticals (flights, hotels, buses, trains, cruises, and holiday packages) plus movies and events. **Shop** is a full e-commerce module with categories, multiple sellers, price comparison, EMI, and promo codes. **Pay** covers mobile recharge and a deals marketplace. Wrapped around all of it sit the loyalty and engagement layers: a multi-programme wallet, offers and deals, gamification, and points.

Loyalty programmes tend to fail at the same point. Points are easy to earn and hard to spend, the redemption catalogue is thin and uninspiring, and the programme lives somewhere the customer never visits. The result is a large outstanding points liability, weak engagement, and a reward currency customers do not really value.

One App set out to invert that by making the loyalty programme the front door to an entire commerce ecosystem, which created a design problem of unusual scale. The surface area was enormous: twelve product domains with almost nothing structurally in common, since a flight search, a cinema seat picker, and a mobile recharge are genuinely different products. Two currencies ran through everything, because every price, offer, and checkout had to work in cash, in points, or in a combination, and the Stars to Points conversion had to be legible enough that people trusted it. Each vertical also carried real domain complexity that could not be simplified away: nearby-airport inclusion and budget-coded calendars for flights, cabin types and sailing dates for cruises, class availability and IRCTC accounts for trains, seat classes with fast-filling indicators for cinemas, watchlists and map views for hotels.

A single loyalty-first super-app, built structurally from the information architecture up.

The defining move was to treat information architecture as the primary design deliverable rather than a preliminary step. Before interface work began, each module was mapped as its own detailed IA mind map, twelve in total running to roughly ten thousand nodes, covering not just the happy path but the filters, sorts, states, edge cases, and content rules of each vertical. That produced a shared, exhaustive specification of a product far too large for anyone to hold in their head, and it is what made a coherent design across twelve domains possible at all.

On a product this large, architecture is the design. It would have been possible to start drawing screens for a flight search in week one and have something to show, but twelve domains designed that way drift into twelve products. Spending the opening stretch authoring exhaustive IA per module felt slow and produced nothing visual, and it was the single highest-leverage thing on the project. Everything downstream, the pattern language, the design system, the client agreement, was cheap because the structure already existed.

A shared rhythm beats individually optimal flows. My instinct was to design each vertical to its own category's best practice, since that is what the standalone competitors do. But the product's advantage was never going to be having the best cinema booking flow, it was having all of them in one place with one currency. Forcing a common search, list, detail, and checkout rhythm cost a little category-specific elegance and bought a coherent app, and that was the right trade.