A social platform where the rewards are part of the product

Social products live or die on the feel of a loop most users never consciously notice: post, respond, return. Adding rewards to that loop is easy to get wrong — points that feel arbitrary read as a gimmick and stop changing behaviour almost immediately.

Building it twice, once per platform, is the other common failure. Divergent codebases produce divergent products, and the differences surface exactly where users compare notes.

Rewards carry a second, quieter risk: they are easy to optimise into the wrong behaviour. Points awarded for volume produce volume — more posts, thinner posts — and a feed that fills with activity nobody wanted to read is worse than one that fills slowly. The mechanic has to reward the behaviour the product actually wants more of.

And a social product has a cold-start problem no amount of engineering solves. Early users arrive to something quiet, so the interface has to make a sparse feed feel deliberate rather than abandoned, and give someone a reason to return before the network is dense enough to supply one.

We developed the mobile app from the ground up for both platforms, designing the user journey so the reward mechanic is part of the interaction rather than a layer applied over it.

Reward points and gamified interaction are built into the core flows, so earning is a consequence of using the product as intended rather than a separate errand.

The interface is tuned for a travel-minded audience — the content people share and the way they browse it shaped the layout rather than a generic social template. Travel content is photographic, place-anchored and browsed in a different rhythm from text-led social feeds, and a layout that ignores that spends its screen space on the wrong things.

Building from the ground up for both platforms, rather than porting one to the other afterwards, is what keeps the two versions honest. The shared journey was designed once and implemented deliberately on each platform, so parity is a property of the design rather than a maintenance task.

A smooth cross-platform journey, with the same product on iOS and Android rather than two similar ones.

A reward system that is part of the experience instead of an add-on, earned through the behaviour the product wants rather than through volume.

A foundation that can carry a second version. Because the journey was designed once and implemented deliberately on each platform, changing the interaction model later is a product decision rather than a rewrite — which matters for a social product, where the loop is rarely right on the first attempt.