Question for u/jeffgadway: Niagara Launcher & hardware mapping on the Clicks Communicator
Hi u/jeffgadway,
Seeing the latest progress on the Clicks Communicator, it’s great to see the Niagara Launcher integration in action—it clearly feels like the right choice for this form factor.
Since the Niagara implementation is part of the core experience, I’m curious about the interaction design regarding the UI navigation. In the latest demo, I noticed the standard "Niagara button" is absent from the screen.
Could you shed some light on how the navigation is mapped for the final units?
Specifically:
Has the functionality of the Niagara button been moved entirely to the hardware, for instance, mapped to the dedicated "red button"?
Or is it triggered via a specific gesture on the display/keyboard that replaces the need for the on-screen button?
I’m really interested in how you’re bridging the gap between the software launcher and the physical controls to maintain that minimal flow.
Keep up the great work—looking forward to the next update!