Back to work
BLUEEYE ECOSYSTEM One ecosystem, two experiences: for the people who live with the system, and the pros who install it.
B2CBlueEye End User Homeowners · monitor & control
B2BBlueEye Pro Installers · configure & validate
BlueEye Pro — mobile app and Paradox wireless hardware
THE STARTING POINT

Powerful hardware, an aging workflow.

Paradox installers relied on a capable but aging ecosystem: wired hardware, dense desktop software, slow connectivity, and an installation process that demanded significant expertise.

That complexity had value in advanced installations, but it also made everyday setup slower and harder.

Powerful, but built for another era.

Capable hardware, aging workflow. Every install depended on a desktop and deep expertise.

Legacy BabyWare desktop software
Legacy BabyWare desktop software with wired control panel and keypad
↳ The legacy system: desktop BabyWare software, wired panel, and keypad.
PROBLEMS

A powerful system with growing friction.

Five frictions held installers back: complex installs, connectivity doubt, a market moving wireless, legacy bloat, and a steep learning curve.

A powerful system with growing friction.

The existing ecosystem offered installers extensive control, but its complexity created several barriers to faster installation and future growth:

Complex Installation

Wired devices, multiple configuration steps, and a dependency on desktop software made installations longer and more demanding.

Eroding Installer Confidence

Connectivity dropped mid-install, leaving installers unsure whether a change had actually saved. Reconnecting and re-checking every step cost time and chipped away at their trust in the system.

A Market Moving to Wireless

Installers and distributors were asking for a modern wireless solution that could be deployed and programmed faster, without giving up professional control.

Legacy Complexity

Years of accumulated settings and capabilities made it difficult to distinguish between what installers truly needed and what had simply become part of the existing system.

Steep Learning Curve

The system's depth was valuable for advanced projects, but its dense structure required significant technical knowledge and experience.

THE CHALLENGE

Build a faster, more reliable wireless system installers could trust.

Build a faster, more reliable wireless system installers could trust.

The challenge went beyond making installation faster or moving programming from desktop to mobile.

We needed to create a reliable wireless experience that restored installer confidence. Every connection, action, and status had to be unambiguous, so installers could see the system responding and confirm their changes had actually saved.

All of this had to be achieved without losing the professional control and advanced capabilities that made the original system powerful.

BREAKING IT DOWN

Not everything needed to come with us.

We mapped every legacy flow with installers and sorted the system into three buckets:

Not everything needed to come with us.

I led the design team through a full breakdown of the existing system and its installation flows.

Together with the product manager and company owners, we mapped the journey from account creation and site setup to device enrollment and programming. Feedback from existing installers helped us distinguish between essential professional controls and complexity inherited from the legacy system.

Every part of the experience was evaluated through three questions:

KEEP

What is essential for professional installation?

SIMPLIFY

What can be made faster and clearer on mobile?

REMOVE

What no longer serves the installer in the field?

Whiteboard system mapping Design team reviewing high-fidelity wireframes Working Axure prototype of the full system
High-fidelity wireframes defining the core installer experience.

Connecting every flow into a single interactive prototype.

1 FIRST ITERATION

Turning a technical system into a mobile workflow.

The legacy installation logic, rebuilt as a mobile-first workflow and validated on real hardware in the field.

The first iteration translated the legacy installation logic into a mobile-first workflow. We focused on the core tasks installers perform in the field: checking device status, configuring devices, assigning actions, and managing system settings.

It was an early attempt to balance professional control with a clearer, faster structure that could rebuild confidence during installation.

First iteration screen 1First iteration screen 2First iteration screen 3First iteration screen 4First iteration screen 5
IN THE FIELD

Validating the flow on real hardware

Screens only tell half the story. I took the prototype on-site and ran the installation flow against the physical devices, watching how installers move between the app and the hardware, where they hesitate, and whether each system state actually matched what was happening in front of them.

Paradox M25EF-8 hardware, rear panel
2 SECOND ITERATION

Expanding the flows around real installer needs.

This round made system state explicit. It taught the hardware and the app to speak the same visual language.

Device LED mirrored in the interface

Expanding the flows around real installer needs.

After the first iteration, we expanded the core flows and made the installation state much more explicit.

Installers needed to understand what was happening at any moment: which site was still in progress, which devices were online, what required attention, and how quickly they could add or configure new devices without losing context.

This iteration made the live state of an install legible: what was done, what was pending, and what still needed attention.

Key Investments
Clearer device status screen

Clearer Device Status

We made device status more visible across the experience, so installers could quickly understand connection, battery, signal strength, tamper, and configuration state without opening every device.

Faster device enrollment

Faster Device Enrollment

We simplified the flow for adding new devices, using scan-based enrollment and immediate feedback, so adding a device took seconds and its result was obvious.

Stronger Installation Progress

“Installation in Progress” became a much more prominent system state, helping installers immediately understand that the site was still being configured and what remained before completion.

Many connected devices enrolled

With many new products added through a fast enrollment flow, how can installers confidently identify, assign, and configure the correct physical device standing right in front of them?

Device LED mirrored in the interface

By mirroring the physical LED directly inside the interface, installers no longer needed to translate hardware behavior into software states. The device and the app now spoke the same visual language, making identification immediate and reducing installation mistakes.

FINAL EXPERIENCE

A faster setup experience installers could trust.

A desktop-grade installation completed from a phone: faster setup and clearer status.

A faster setup experience installers could trust.

The final experience transformed a complex desktop-based installation process into a clear mobile workflow for wireless systems.

Installers could create a site, enroll devices, identify products, configure settings, and understand every system status directly from the field.

What Improved

Installer setup time cut by over 50%

Installers completed the entire wireless setup directly from the app, eliminating desktop dependencies. Measured across live deployments, the redesigned flow cut typical installation time by more than half.

Greater confidence with fewer support requests

Clear connection, battery, signal, tamper, and configuration states helped installers understand exactly what required attention before escalating issues.

Faster enrollment for multiple wireless devices

Scan-based enrollment and immediate visual feedback made adding multiple devices faster, simpler, and more predictable.

Positive field validation from installers and distributors

In field testing, installers moved through setup with noticeably less back-and-forth, especially when identifying devices, checking system status, and confirming a change had saved.

FINAL DESIGN

Designed for focus in the field.

A darker, field-focused UI, built on a full design system that still evolves today.

Designed for focus in the field.

This version introduced a darker interface that reduced visual noise and helped installers focus on system status, device configuration, and the next required action during setup.

Final design core screen 1
Final design core screen 2
Final design core screen 3
Final design core screen 4
Device programming screen 1
Device programming screen 2
Device programming screen 3
Device programming screen 4
Device programming screen 5
Device programming screen 6
Device programming screen 7
Device programming screen 8
Aviram Lagrisi

Want to hear more?

Behind these screens are years of research, trade-offs, and decisions I couldn’t fit on one page. If you’d like to hear how it came together, I’m always happy to talk.

Contact via WhatsApp
COLLABORATORS

🖤 A pleasure to work with.

Product Designers

Gleb Lobovsky Shani Gabay Yarden Tzafrir Cristina Gromov

iOS & Android Team

Israel
Moran Yona Ofir Mashash Qusai Assad Syaueb Assad
Romania
Bogdan Perianu Andrei Florin Moneanu

Embedded, QA & Server

Canada
Steve Corbin
Miami
Jordan Peles
Israel
Hadi Mrih