Yes. But why would you need that? I mean, our experience shows that customers don’t want to do anything, most of them like the things to be done by someone else. In other words - do you think it is a good idea to ask the customers to set up something, instead of doing it yourself and maybe take a money for that as well?
I get what you mean, what the customers wants in our case is access to the data on their phone/tablet/computer in general, some definitely won’t mind or would prefer setting up the UI themselves, most tech literate people will be able to manage to build a Blynk template if the datastreams are configured already. Of course others will probably want to just have something finished and working out of the box. Managing their UI updates especially as an upcharge is good but also would take more manpower.
Could you please give more info about your use case? Why do you think your customers will/want make some setup of templates?
The background is we are taking data from older ‘dumb’ devices that have been used in certain industries for decades and turning them into ‘smart’ devices. Especially if the resources are spread over lots of locations, for example to see if your pump is working you have to be on site and look at it or wait until your storage tank overflows and you notice the problem. But we can let them see how often the pump runs, and the level in the tank so they can check the status of their sites anywhere.
Even when companies offer newer smart versions of the hardware nowadays, if the old infrastructure still works it is hard to justify spending tens or hundreds of thousands of dollars and downtime replacing everything just for a new model that does the same thing but can show you info on an app, vs a smaller installation and monthly fee to tap into the old hardware and get a customized real time and historical data feed without rebuying everything.
A further use case is right now the company that services certain infrastructure has to send someone on-site if a problem cant be resolved over the phone (and that can only be done if the customer explains the problem properly). So we can now give the service techs a real time view of what’s going on and they might be able to guide the customer on how to fix the problem without having to go on-site. So we could have a simplified customer facing template and then an advanced template that the tech can configure/edit to show what they want to see.
I’d say that people do like the ability to customize things how they want, and in our case they might have 100 things to monitor but only really care about 5 of them, and if they start having issues on some device or location they might want to adjust their dashboard and focus on that location so they can see it at a glance as they figure out what is wrong.
But some will just want to see a few fixed values and that’s it, and its easy for us to build the dashboard in that case.
I think it probably is the difference from most of your business customers building a fixed hardware device that they want to mass produce (I assume) and has a limited scope of data it needs to display, compared to my open ended and unique-to-each-customer use case where they are reaching out to us looking for a customized solution. As long as we can get the data off the hardware and set up a basic interface showing that they can see the data on their phone now they are happy, and being able to customize it themselves, in my opinion, is actually a selling point!