Platform for kiosk software

Hello everyone I got a task to develop software for kiosk machines (machine like passbook print machine), which platform is best suited for development (windows or web) which should will give more command over the local system and software updates with less maintainance work. Kindly suggest

I've never done this sort of project before, so take my words with a grain of salt. Putting some thought into it I came up with these points of note:

If the kiosk can be configured to run a fullscreen web browser, it might be an appealing option to go with the web-based solution. This would allow you to push updates without having to affect any of the machines, since it's just displaying in a web browser. The updates are automatically recieved when the browser is reloaded.

If the kiosk is a touch screen device and is supposed to look like a fancy app, then consider trying Blazor, which would allow for some fancy touch-friendly web apps / single-page applications. But either way, with the web application path--since it's in a web browser-- you can use any technology stack that makes the most sense to you or your business needs.

If your kiosk needs to interface with more than just a server, eg reciept printer, cash drawer, or other local hardware devices (like in a POS system), then an application installed on the kiosk would be better suited. I think. The setup and updating process would be more difficult, however.

"which will give more command over the local system?" - locally installed application written in the native language of the OS

"which will give me more command of software updates?" - web application

"less maintainance work" - web application (I think)

These are my opinions, please feel free to critique my thought process.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Devendra Kumar6y ago
I heard about Blazor but there is an issue at both the ends
Server side requires continuous touch with server, any sorts of disconnection leads freezing to the application and it will wait for the server to re-connect it, in the meanwhile user can't interact with the application.

On the other hand Blazor webassembly is not ready for production use.

Can you put some lights on the thoughts above.

Thanks
Devendra
0
Sean Franklin6y ago
I've never done this sort of project before, so take my words with a grain of salt. Putting some thought into it I came up with these points of note:

If the kiosk can be configured to run a fullscreen web browser, it might be an appealing option to go with the web-based solution. This would allow you to push updates without having to affect any of the machines, since it's just displaying in a web browser. The updates are automatically recieved when the browser is reloaded.

If the kiosk is a touch screen device and is supposed to look like a fancy app, then consider trying Blazor, which would allow for some fancy touch-friendly web apps / single-page applications. But either way, with the web application path--since it's in a web browser-- you can use any technology stack that makes the most sense to you or your business needs.

If your kiosk needs to interface with more than just a server, eg reciept printer, cash drawer, or other local hardware devices (like in a POS system), then an application installed on the kiosk would be better suited. I think. The setup and updating process would be more difficult, however.

"which will give more command over the local system?" - locally installed application written in the native language of the OS
"which will give me more command of software updates?" - web application
"less maintainance work" - web application (I think)

These are my opinions, please feel free to critique my thought process.
0