I want to learn ELM (not started yet) while simultaneously producing something of value in the form of an open-source project. I plan to read this korban.net elm book in parallel to a simple project.
A local coffee shop has asked for a very basic POS. They literally need their 2-3 waiters/waitresses to tap on ordered items on their phones / ipads and it would generate an order.
This project, EpPos, is good enough and is what I have installed to start with.
One behavioural attribute I am contemplating changing is, it requires a central API running on the local server to do the calculations. It is a solid approach but requires an always on box in a cupboard and if that goes down, so does the system.
I was thinking about whether it is possible to have the entire system running locally in a web app.
The way I am thinking, 2 or 3 devices with my POS web app installed called interact to manage the current value of the till register. All calculations would be complete on the device (simple additions and subtractions).
I think this kind of distributed system would be nice but would interfere with my learning. For starters I am going to keep to a Django REST API as a centralised backend because I know it (later I would like to learn more about whether GraphQL could solve some problems I might have with REST) and I could inherit from the EpPos project linked to above, except write an Elm frontend for it.
Do you think this is a good tinkering project to do in Elm?
Any feedback and discussion about the potential pitfalls in my idea are very much welcome. I am not married to any ideas.