Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add Point of sale data to the dashboard
See original GitHub issueAs of 1.5.0 we currently only have dashboard data for the crowdfunding. We should add it for the point of sale app as well.
It can be very similar to what we already have for the crowdfunding, displaying total sales and best sellers products in a pie chart.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Navigate the Square Dashboard
The Home section of your online Square Dashboard provides a quick look at the status of your business through sales metrics. These key...
Read more >Get Started with the Square Dashboard App
Easily access statistics and data about your business with the Square Dashboard widget. You can view gross sales, net sales, transactions, average sale, ......
Read more >Point of Sale Dashboard
This dashboard provides a filter, so you can easily see data of any POS like if you want to see data from POS...
Read more >Introducing ADD's NEW POS Sales Dashboard & Scorecards
The POS Dashboard gives a real-time, immediate picture of the entire store, including transaction counts and sales by category, for each store.
Read more >POS Data Analysis: Make Data-Driven Decisions
Point of sale (POS) data helps you understand how your physical store influences customer loyalty, how much they spend online and in-store, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Dashboards is a hard topic, in normal company you have teams dedicated only for that. If you want a dashboard that doesn’t blow up in response time, it needs quite radical backend work. (For example, just showing the balance of NBX in acceptable time took me a month of work, it was taking 5-10s before, and even saw more than 1 min for some people)
Having separate tables to maintain the stats is the way to go, but then you have to solve other problems: How do you keep the data up to data? Triggers? materialized view refresh periodically? App side? Does the stats need to be accurate or approximate?
This is more than we can chew for now.
I also believe it is strange from UX point of view to put everything in a single page. If there is too much information, the user isn’t likely to find easily what he wants in it. (need to scroll down and scan all page looking for it rather than just clicking on a separate link)
I have an instance using apps quite heavily so I’ll see how the current response time is affected and see if we can’t go with what @dennisreimann already did. But next release we will need either heavy re-work on the backend, or splitting the data in several pages as this is not sustainable to continue that way.
How about adding JSON endpoints for most of the tiles, so that we can display the dashboard fast initially and those data intensive tiles fetch their data asynchronously?
We’d need something like this anyways for tiles where the user might change something, like the time period. We have this for the wallet balance already.
I agree that the current approach isn’t scalable, but I don’t think that having a separate dashboard for the PoS data is a good option. The above seems to me like the best way forward regarding the performance.