distribute = share so that everyone can use the same device together
I’m not a business, I just want some users in the house to have less feature access to the same device hence different apps.
I can see the business value if you want to distribute 100’s of devices and not have to pay to clone the apps and perhaps aggregate lots of hardware data in one place for a web dashboard but again that is not what I need here
tapping in a pin every time i start an app to unlock features is not very user friendly and the target is having to parse that and get involved by sending back vpin widget changes? also all those widgets are visible even if they may not be active ? and non-expert users don’t want to see a terminal that is just plain ugly they want to see nice buttons and sliders simple controls only
yeah time input widget, the ESP would do the time compare and turn on at correct time not asking the app or blynk library to do any timer services as Ive already got NTP and local time correction on the target
come on … that is not fussy that is design for purpose
a terminal is a bit ‘technical’ to be putting on the screen of a simple users app but perfectly fine for me as the designer/expert user of the devices
I really appreciate that you are giving me some good technical answers to this problem, thank you
but it really is not nice to have disabled widgets and terminals in a ‘simple user’ app even when on other tabs, it is just not clean design.
I’ll use some of your suggestions for now but the original topic question still stands …
I’d like to be able to write a small group of different blynk apps with slightly different purpose talking to a single hardware instance
If in the end it means a business license would be needed for this hinted at feature multitenancy? (not made clear what that is and no clue searching your site) that is no good for a home user like myself
Thanks to everyone who replied to this topic. I’ve learned a few things and have a few things to study more. I’ll summarize my general thoughts here and then post a corresponding topic in the “Ideas” area.
After reviewing many other topic threads on related issues, it seems there is a significant need from the Blynk community for the topic subject. Granted, it may be in development for business users, but I personally think it would serve hobbyists as well as business users if this capability were more directly supported at all levels. Let’s face it, business adoption usually stems from individual user adoption. While it appears there are potential work-arounds to support multiproject-to-single-device capabilities, the current state of the system does not lend itself well to most casual end-users that need to see data across devices.
I’ll also share another way to think about this capability from a higher level. I think the Blynk infrastructure would benefit immensely from a capability to create projects with different “VIEWS” into the underlying hardware. Doing so would open up huge application possibilities that could benefit the techie-nerd like myself all the way to the non-technical end user that is pointed to a friendly mobile app that they just use without any understanding of the underlying architecture.
Finally, I understand that technology evolves gradually and Blynk is no exception. I personally think that Blynk is a truly awesome platform that helps IoT developers like myself move from idea to working app with incredible speed. Thanks to all of you who work so tirelessly on the Blynk project.
There apparently is a text input widget on the development table…
There isn’t… I said it, and widget lockout, it was a feature that has been requested… whether it is to be done or not is up to the developers…
Meanwhile something like it can be implemented (well the widget lockout part) via code and PIN or touch pattern codes, etc… As with most everything technical with these MCUs, your imagination and coding skills determine the results.