81–90 of 94 posts
I hate this modern design trend of wasting as much of my screen real estate as possible. It's ugly and it wastes my time, which is rude. Every one of these tables is literally 300% taller than it needs to be. Get rid of all the pointless padding and spaces. You can pack 3x the information on screen. This looks "modern" but it doesn't look good and it certainly isn't useful . Every time I bring this up in UX review de…
Earlier quoted context omitted.
- personal finances - get statement exports to sqlite db and I have dashboards to manage expenses/finances, retirement account data in sqlite and charts for actual and projections - my car - I collect data in sqlite db - amortization schedule/actuals for the loan, fuel/maintenance expenses etc. Dashboards on top of it with metrics such as $ spent, miles, cost of finance, cost of ownership (per mile) etc. - workouts -…
Thanks! Can you share screens of your car dashboard, this sounds like a marketable simple one-page web-app that people would sign up for an use... But then you'll get millions of users and you'll have to learn postgress and a range of other meta-metrics to track your uptime and availability 9s to your constituent users....
Earlier quoted context omitted.
Which templates do you use?
I've shelled out $$ for https://tailwindui.com/ Currently using their components, but will (re-)use Primer for a private project https://tailwindui.com/templates/primer
I love Tabler and have used it for a few projects with great success. The title of the OP is not really accurate though. It's not so much a framework but a bunch of customization on top of Bootstrap and some pre-built templates for stuff _like_ dashboards, galleries, forms, etc. The site is more like a kitchen sink demo and documentation site for stuff you can pick apart and use in your own application.
How do you approach building on top of a dashboard template? > Any change in /src directory will build the application and refresh the page. Do you start from the demo page and start ripping off components that you don't need? Or do you pick specific parts from the template and build it from scratch from bottom up? Even though templates seem to be an easy way to build stuff, I never understood the approach building f…
Dashboards are usually quite unique depending on the data they display and purpose of them, so just ripping the demo isn't necessarily going to be the best approach to go with.
In my case I'd start with choosing a layout and throwing together a rough sort of navigation menu, and then building each page by scratch (or based off previous pages). It's as simple as browsing the demo to find which components you need and then just copy / pasting them, either directly from the demo page or from the documentation.
The only times I've ripped entire pages have been for auth pages, error pages, etc - i.e. pages that are usually quite common to all applications. I find that it's better to take a standardised approach for these pages as it's more intuitive for the users rather than reinventing the wheel.
Earlier quoted context omitted.
I’m talking about the whitespace within a row. There’s no reason to make a row in the table 3x taller than the text on the row. If you think 8 rows is all your users need that’s fine, but why waste all that space?
Well there is a point to be made that if you don't stack rows without any spacing the user might actually be able to look left and right at different columns without losing sight which line they were even looking at. Can be partially solved by having alternating colour rows (and frankly it should've been a thing here), but ultimately this is far easier to read then your average excel sheet, at least to me. And frankl…
Are there any good reasons to use this instead of Tailwind? Is it mainly just the look of the components?
Way less work? Tailwind is on a lower level of abstraction than this.
The better question would be: "What is the difference between Tabler and using Bootstrap or Bulma or some other framework?"
Earlier quoted context omitted.
Well there is a point to be made that if you don't stack rows without any spacing the user might actually be able to look left and right at different columns without losing sight which line they were even looking at. Can be partially solved by having alternating colour rows (and frankly it should've been a thing here), but ultimately this is far easier to read then your average excel sheet, at least to me. And frankl…
My eyes get lost in the expanse of empty pixels. Tight packing makes visual scanning easier .