Increase API surface

[Epse]

This should allow new front-ends to be developed (as well as possible native clients).

What we currently miss:

• Authentication via API
• A JSON addition

And way of using the current API's (like reset_order) that return the entire page, without getting the entire page.

[dnk8n]

I am viewing your project in the hopes that I can get it running in a local coffee shop. If it works and I spend more time on it, I am keen to look into GraphQL.

Here is a tutorial on integrating it with Django: https://stackabuse.com/building-a-graphql-api-with-django/

GraphQL is meant to have some advantages over REST, especially when supporting many different types of clients.

[Epse]

GraphQL is definitely interesting. My big problem with this project is that I don't have any feeling with what an actual potential user would want out of it, and what could be improved. I'd be immensely grateful for just that information, because as it stands, I don't know where to go with this.

[dnk8n]

What steps do you recommend for a user like me?

Should I get this code running on a server and then test it out in the coffee shop, then provide feedback?

Any more detailed steps would be appreciated :)

[Epse]

What platform are you on? If you install docker and docker-compose, you can simply bring up the container on any machine and give it a go, should be fairly simple even to just try out at home. You probably want to try at home before going to your shop though ;)

[dnk8n]

Yeah, your instructions are perfect.

I tried it and all is working nicely. Given it to the shop to play with since I need to hear quickly if they need more functionality and how much more.

I will then decide if I can extend this, or suggest a more complex system.

But simple is better. I think you should keep it as simple as it is. I always like the ability to make things more feature rich as an option, rather than being forced into it.

I found some features which I would like to see in a minimal viable product, I will make separate issues about them.

What I meant in the question before, was how can I best help you. If there is any particular information you are interested in from me, I would be more than happy to oblige.

[Epse]

Thanks! I'd mostly be interested in the kinds of interfaces that get used (probably a touchscreen I'd guess) and how well the multi-user system works. Also things like the importance of keeping old transactions around, or the count of how much cash should be in the counter. Maybe if you want additional payment methods (perhaps configurable). I also had this idea that some places use portable devices that servers carry around to make orders, which are then completed by someone else somewhere else. As it stands, each user can only have one order open, I don't know how much of a problem that is. May 10, 2019, 3:11 PM by notifications@github.com:

…

Yeah, your instructions are perfect. I tried it and all is working nicely. Given it to the shop to play with since I need to hear quickly if they need more functionality and how much more. I will then decide if I can extend this, or suggest a more complex system. But simple is better. I think you should keep it as simple as it is. I always like the ability to make things more feature rich as an option, rather than being forced into it. I found some features which I would like to see in a minimal viable product, I will make separate issues about them. What I meant in the question before, was how can I best help you. If there is any particular information you are interested in from me, I would be more than happy to oblige. — You are receiving this because you authored the thread. Reply to this email directly, > view it on GitHub <#63 (comment)>> , or > mute the thread <https://github.com/notifications/unsubscribe-auth/ACMMVK7K7CPOPVVQG3JFGVTPUWGBFANCNFSM4FYHDJRA>> .