IsraelMoses Busharira
← Contents

Chapter 01

Flentra for Events

Getting a whole crowd through the gate, and not one fake ticket.

It's 7:40pm. The headliner is on at eight. There's one steward at the gate with a phone torch and a printed list of ticket numbers.

Somewhere in the queue, three people are holding a screenshot of the same ticket.

the kind of night Flentra was built for.

The product

The gate is where the whole night can break.

Ticket fraud, slow manual checks and disconnected entry systems cost organisers revenue and reputation. Attendees arrive to long queues, duplicate entries slip through, and when something goes wrong at the gate, staff need something reliable to fall back on.

Flentra for Events is a Pinnisoft product, one of the Flentra family, built around one moment: getting in. Implementation details belong to Pinnisoft Ltd, so the journey is what I can show you here.

How it works

The gate, split in two.

The attendee journey runs across separate touchpoints, each with its own interface, all sharing one live data layer. The key idea: validate away from the gate, hand over a wristband, and let the gate do a single one-tap check. Two quick checkpoints instead of one slow one.

Organiser dashboardSet up the event, ticket tiers and capacity, then watch the doors fill in real time.
Attendee ticketA QR-coded ticket in your inbox and SMS. Nothing to print.
Validation tentStaff scan against the live registry. Duplicates and screenshots stop here.
Wristband at the gateA second, one-tap check. The gate only has one job, and it does it fast.
My part

A redesign, and a steadier product.

Flentra was already built and running events when I picked it up at Pinnisoft in 2026. Working with the team as the front-end developer, I redesigned the interface and put a lot of work into making it more stable, so it holds up when the queue is at its longest.

The apps are built in Flutter and the website in Next.js. It's very much a team product. My job was to make it look and feel as dependable as the idea behind it.

From the build

The Flentra website.

the website, in Next.js: verify a ticket or download the app, right from the top

the track record: real events where Flentra has worked the gate

Try it yourself

Walk the attendee journey.

…and yes, try sneaking in with a screenshot.

  1. 1Buy
  2. 2Ticket
  3. 3Validate
  4. 4Wristband
  5. 5Gate
  6. 6Inside

Flentra Live · Kololo · Saturday

Grab a ticket. Whose name goes on it?

Flentra at the gate
45s → 8sAverage validation time per attendee at pilot events, before and after Flentra.
0Duplicate entries recorded across all pilot events.
LiveOrganisers see real-time attendance as the doors fill.
Looking back

I'd do again

Respecting what already worked. Stewards had learned the product under pressure, so the redesign kept their habits and changed the parts that slowed them down.

I'd do differently

I'd test the redesign at a live gate even earlier. A packed Saturday night finds problems no staging server ever will.

Turn the page · Chapter 02Bulamu Bridge AI →Maternal care that doesn't stop where the road does.
Bulamu Bridge AI cover