Beginner- program logic within app

HI - new here so apologies if obvious, but I have looked!

I’m struggling to understand where I integrate the program logic within my Android/ Ios app (ie this is the app, not the code on the remote mpu hardware). I have a project to add a connected controller to an existing piece of control equipment (an HVAC system in a server room). My app will have some simple controls, and I understand how to add these to the app UI (thing like a ‘turn it all on’ button and a ‘go into turbo mode’ button’ etc)

What I DON’T understand is how to apply logic in the app - for example the hardware will send the app regular data - for example “the temperature is”, “my voltage is”, “my safety gate is open”. I need to apply logic to this locally on the app NOT at the hardware device. So I might have a ‘trigger temp’ set on the app, and then want the app to sound an alarm if the trigger temp is reached at the hardware. AND the door is open (I’m simplifying, but hopefully making the point of needing program logic at the app level).

Ultimately this is a commercial/ semi commercial project, and I want to connect multiple app users to the same piece of hardware - each app user will have their own specific requirements, hence the wish to keep the remote hardware simple (ie receive and stream data) and keep the logic and rule in the app. Am I asking too much of Blynk or have I just missed the point?

Hello. We have all this.

For app logic - http://docs.blynk.cc/#widgets-other-eventor (not yet available on iOS)
For sharing access to hardware - http://docs.blynk.cc/#sharing-shared-access-to-your-hardware

Thanks for the quick reply - that’s encouraging!

Any ideas for timescale on iOS implementation, I’m not sure I have the option to restrict myself to Android only?

Secondly (and this is real beginner!) does the app on the phone run continuously in the background even when the phone is sleeping (and thus can produce such alerts) - if so is this likely to have a huge battery impact?

No, of course. This is done by server.

Thanks - makes sense! Timescales for iOS?

For eventor? Not sure, 3-6 months. We are busy with business clients right now.

Eventor widget provides an interface to describe the logic to be executed on server. So, if, say, you used Android to setup Eventor widget in your Blynk product, the logic would work for both your Android and iOS end-users.

3 Likes

Great news - understanding the logic works on the server and the Android is only for set-up makes a huge difference. Thanks.

1 Like