How to make Neeo the best-in class universal remote ever

Raphael

I am conscious that there is a long way to go before Neeo's firmware meets users expectations. I am conscious that the product must provide some trendy and buzz-compatible technologies to get visibility on the market.

But I believe that there are core features for a universal remote that Neeo team should not forget, whatever are the amazing innovative features Neeo is bringing to us. For sure you are conscious of this (IR learning is coming soon...).

Neeo is working hard to offer a simple innovative setup experience but, for me, this is done at the expense of user UI and usability.

Best evidence of this is that there is not even a discussion room for the Neeo UI on Planet Neeo. Hey guys: do not forget that a remote is first of all a IHM and that the target is to bring usability to non-geek people at home!

How such a top technologies-enabled device can be far behind the old Philips Pronto, URC, RTI, Nevo or Harmony in term of usability?

Attached you will find a feedback of what my current Nevo S70 remote is doing and what I achieved with my Neeo so far. I am learning and did not dive into Node.JS drivers but I never dived into code with my old Nevo... 

My intend is not to explain that Nevo was better. Nevo products (and Pronto and others) died because of buggy OS and communication features (Wifi / Zwave) and because of a too complex UI designer.

You addressed the communication and the setup with your modern frameworks. Do not forget to address the user UI. We cannot even customize the 'Welcome" to 'Bonjour' or set a custom background on the screens.

If of any interest, I can even donate the vintage Nevo designer software bundled with the Nevo and even send you my second Nevo SL remote which gives similar UI experience to give you ideas.

Perspectives on Neeo are great but perspective do not make the remote usable for my family for the moment. I have no free time left out of my business otherwise I would love helping more.

Reply
4replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Nice and constructive post, I am totally with you and I believe that NEEO is as well. I would like to address some of your points in the PDF.

    - stupid device (power toggle) the solution that is currently in beta is working really well. Expect it soon™️

    - Kodi not showing transport controls. This is due to the driver you’re using. Please share your Kodi setup and the driver you’re using. I’m sure there is a solution already.

     

    I would really live to be able to do some customization to, especially a new background would be a nice start. The current one isn’t bad at all but it gets a bit boring after a while.

    Reply Like
  • Yann FREMONT said:

    do not forget that a remote is first of all a IHM and that the target is to bring usability to non-geek people at home!

     I think you raised a central issue. A UI for replacing remote controls for various devices and also including actors and sensors will have to deal with all the different purposes and options and therefore is not an easy task. Nevertheless it has to be addressed in future releases.

    From my point of view and my experience with UIs there are a few principles that need to be considered a bit more:

    a. The main tasks should be very easy to accomplish, more complex items could be "hidden" behind an expert mode that needs explicitly to be turned on. If this expert mode for efficiency reasons requires more screen area it then maybe will work only in a browser or an app on a tablet, not on a smartphone.

    b. The recipe UI is suitable for smaller tasks but not very efficient for complex or longer ones. Steps where there is a high probability that they will have to be repeated in a recipe need to be handled more efficiently. I have included the example below also in a previous post with my initial feedback.
    - Example: If you need to send 5 times the same cursor step with a delay in-between you have to set up ten steps and when you need to edit the delay time after it requires 5 additional edits. A better solution would be to include a repeat counter and a delay time(r) with a default of 0 on each send command screen. Like this 5 cursor actions with a delay in-between can be set up in one go and modifying the delay only needs  a single edit.) 

    c. The display of a status should not address and include the most relevant attributes and functions (audio is on - show station, song title playing, ... / TV is on - show channel icon /  RGB light is on  - show color set / sensor - show current value / ...) 

    Regards

    Leo K.

    Reply Like
  • Leo K. said:

    c. The display of a status should not address and include the most relevant attributes and functions (audio is on - show station, song title playing, ... / TV is on - show channel icon / RGB light is on - show color set / sensor - show current value / ...)

    Pleae note this small but important correction to the part of my previous post quoted above. Please ignore the "not", of course I meant that the display of a status should address and include the most relevant attributes and functions.

    Regards

    Leo K.

    Reply Like
  • One idea about status: same layout as in Android with small icons and a drawer would be great. Sliding  the drawer could give access to the list of devices On

    Reply Like
Like2 Follow