Case Study · Bradesco

Off-the-shelf technology wasn't up to the task.

A touch screen kiosk for Bradesco to showcase its web and mobile solutions. For the experience to work, we had to build both the hardware and software from scratch.

Physical-digital installation
Custom hardware
Software engineering
36
simultaneous touches detected
36 GB
of chroma key footage
6
actors in the experience
1
piece of glass instead of three
01 / THE PROBLEM

The bottleneck was in the glass, not the content.

The pre-installed touch screen technology provided a poor user experience. No new interface layer would fix it: the touch failed before it could register as a command. Redoing the content on that foundation would just be masking a physical problem.

02 / THE HARDWARE

A frame that didn't exist on the market.

In partnership with an international supplier, we developed a custom infrared frame capable of detecting up to 36 simultaneous touches. We imported and installed the hardware. We also rebuilt the physical structure: the old three-piece glass setup was replaced by a single piece, eliminating the seams that interrupted gestures mid-motion.

Thirty-six simultaneous touch points, enough for several people to explore the kiosk side by side without fighting over the screen.

03 / THE SOFTWARE

36 GB of video running in real time.

The experience features six actors filmed on chroma key: 36 GB of footage that needed to be called, composited, and discarded without a stutter, at the pace of the visitor's finger. We wrote the software in C++ using the Cinder graphics library, with an advanced memory management system and rendering optimizations to handle the files in real time.

The result is a navigation experience where users explore features, simulate operations, and understand the bank's product benefits without ever noticing the engineering supporting every frame.

Record

The installation in operation.

Project record · Lemonade archive
Why this project matters

Nobody asks for an infrared frame.

Bradesco asked for an experience that actually worked. The gap between those two things is exactly where Lemonade operates: when a project demands it, we go down to the hardware and C++ level instead of adjusting our ambition to what is already available off the shelf.