Outsystems on a displayless wearable
Question

I am working with a customer who wants to use a smart band as a first responder device and get it to detect a wide range of biometrics, location etc. and transmit the information to a first responder app.

The key is the smart band must be as inexpensive as possible as it will be lent out to thousands of people in clubs/festivals etc. So, to reach the low-cost point, they would like to have one made with no display, just a button to trigger a panic alarm. The first responder app would show the location and warnings coming from the devices.

Is there a possibility to use Outsystems .e., can I build a headless app for the device using Outsystems or must the app have a display? E.g. is it possible to create a web service running on the device, built with the Outsystems platform?

Much appreciated

mvp_badge
MVP

Hi Marc,

It would help if you would share technical details about the wearable, as that pretty much will help use to tell you if it can run an OutSystems application. But in general OutSystems applications (web, pwa) are run in a browser session. So if your wearable has a browser built-in, you should be able to run it. That said most likely the application will not able to use any of the wearable features. Also the type of browser if any is available in the wearable might not fully support OutSystems.

Some other answers to questions you asked:

  • "must the app have a display?",
    No you can also create OutSystems API's (REST and SOAP) that then can be consumed by other (non-OutSystems) applications.

  • "is it possible to create a web service running on the device, built with the Outsystems platform?"
    • Webservices don't run on devices they run on the OutSystems server. You can however call OutSystems services from any other platform as long as it has connectivity to the OutSystems cloud,

My guess is that running OutSystems on the wearable will not be a workable or performant solution. The wearable probably has its own development platform, and that platform can consume REST or SOAP services created and hosted in OutSystems.

Regards,

Daniel


Hi Daniël, thank you for your advice.

Still in Discovery stage and haven't yet decided on the wearable, as I wanted to ensure first whether an Outsystems application required a display or not, as that would impact cost.  We have a device designer involved to advise on the build/buy decision. 

I currently have developed a test Outsystems mobile application to ensure full access to sensors and developed a REST API for external app connection.  However, it is running with a display.  From your reply I take it that it is possible to develop one to run on a display-less device?

Sorry for clarity by 'web services' I meant a 'service application': https://success.outsystems.com/Documentation/11/Developing_an_Application/Reuse_and_Refactor/Use_Services_to_Expose_Functionality  thinking that this is a way of implementing an application in my context of a display-less device, running on the device and transmitting information as a web service via a REST API to remote applications.  Would this be an effective way of providing a headless application on a device?

Much appreciated

Marc

mvp_badge
MVP

Yes, I agree that an OutSystems REST API can be used to provide a headless application to be integrated with a device, assuming the device can consume the REST API.

Yes, my current Outsystems Android app is already consuming the REST API I have exposed remotely - so I am hoping I can port it to a display-less device.  You have given me hope! :)

Thanks again

Marc

Hi Marc,

On top of the previous reply, I want to highlight that there are supported components already implemented that integrate with the HealthKit API for iOS and Google Fit API for Android:
https://www.outsystems.com/forge/component-overview/11715/

This would be the typical scenario to integrate with wearables: Either via supported SDKs, or APIs provided by apps that can run into the wearable.


Hope this clarifies your question.

Hi Daniel,  thank you for your help.

Yes, those APIs were the first thing I looked at and they may figure in the final implementation.  There is a wide range of health and safety risks that we want to detect - for example, poisoning, heart attack, severe pain, stress etc all of which we are developing algorithms.  These more general sports and nutrition APIs do not cover these more specialised use cases of course, but I will investigate more - a great suggestion.

The device will need to support an indoor location and tracking algorithm on board too - thus contributing to finding out whether we can develop a native Android mobile app on the Outsystems platform, functioning on a display-less device. As an aside, it also appears that I will have to use Cordova to access the sensors. The final option I guess would be to develop a full Android app without Outsystems, but then face losing all the associated benefits.

Thanks again

Marc

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.