I would like to check for firmware updates from the app and update the phone from the app without having to touch the remote.
Remote itself is enough capable to handle these tasks. we don’t want to code everything around the phone app because they are dependent on Google Play store or Apple App store policies. Nor the remote is low resource controller, it is an Octa-core Arm which runs Android itself. So no point here to do updates from the app.
1 Like
There is a huge reason to do updates from the app if the person wants to, as an option, and that reason is for convenience. I want to do it that way because it is convenient to me. If it’s something that doesn’t take a huge amount of resources to implement, it’s something you should do because it’s feedback from a user who wants that added convenience.
That doesn’t mean that everybody has to do updates from the app, you can still continue to do updates from the remote itself. But having the option to do so, makes the remote more convenient to use and work with, and convenience is something you should be taking very seriously.
Now imagine for that Haptique needs to send data backward to the server, here is where most of users hate the product which sends data back somewhere. To be honest what do you setup from the Haptique is what we do not want to know. We just have a config app which will send configuration to the remote and not the other way around.
This is why we do not get any information from the remote, so here in your case we need to check with our server application to know the firmware and then trigger a connection back to mobile app which will give a notification to ask you to update via a push button. Now the data will flow from config app and force Haptique to update.
In a nutshell we are trying to make Haptique least interacting with the server as the norms today for local first systems.
1 Like
Are you planning on this remote being a developer’s device or are you planning on this sitting in media rooms where the user simply picks up the remote and uses it as intended? This is the issue you have to address with usability- the person who wants to pick up the remote and use it without having to reconfigure and whatever are not going to want to sit there with the remote and figure out how to update it. The vast number of iPhone users- who are the vast majority of the people who can afford this remote- are familiar with an app giving them a notification on their phone to do something. opening my phone and clicking a button knowing that my remote is updating when I am not using it is a convenience and as for the data traveling back and forth with your servers- I could not care less. What are you receiving? The version of the software on my remote? who cares? And if someone does- that’s why you ned to make it OPTIONAL for those who want to enable it.
Why not simply take the best of 2 worlds, set a notification that there is an update available in the App. This way you get notified but it’s up to you to decide is you want to update. Working 30+ years in this industry updates can cause issues that weren’t there before. As long as the remote functions as an independent remote control I personally wouldn’t touch it.
UPDATES is a ‘thing’ that we need or want to do because we think it is better, it actually isn’t always.
Back to Haptique YES new functionality is added but I don’t always want to update.
The “best of both worlds” would be to have the option to update the remote remotely from your phone. That would make it an option- again, if someone want to update the old way they can.
You should add access to this community and related support directly in to the app.
There is already link to Support website. There you find the community. It is better this way because we never saw any community link integrated in the product ever there is reason for that.