Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's a point-of-sale, so I would assume a GUI would be best. Maybe not though? Why would a non-GUI program be an advantage for a point-of-sale application?

It could be a webapp, sure, but it needs to be able to print and interface with a printer properly... I suppose a custom style-sheet could take care of it. Do you think a point-of-sale webapp is a good idea?

And yes, I know I have a ton of choices, which is why I came here for advice. I respect and value HNs opinions.



Being point of sale, it would be best to build a GUI app. Airports especially "still" use non-GUI apps (possibly due to the cost of upgrading), but it'd be far nicer for your end users to provide a clean and clear way to work with your application.

If it were to be a web app you could (for example) use a PDF library to produce receipts and handling printing that way. In this case, you could also provide a simple and clear way to customise the receipts.

Certainly the advantage of it being a web app is that you wouldn't specifically have a requirement for Linux (if for example they already have a set of workstations) or installed applications. This would mean that implementation would be far easier and say, managers could quickly pull up the POS system for a specific client in the back office.

The only issue I can see with a web app solution is interfacing with hardware. You would either need to forgoe the possibility of hardware, or work out a way to interface them.

I think there are countless possibilities, most of which will be rather dependent on the local businesses. They seem to have provided you with a lot of breathing space, so it may well be that many solutions will fit and you are free to choose which would work best for you.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: