4 ms·
This is a very minor point, but I just happened to be checking your site on a laptop with a 1366x768 screen. At this resolution, the "easy to use" button actual
by wanda 9y ago
This is a very minor point, but I just happened to be checking your site on a laptop with a 1366x768 screen. At this resolution, the "easy to use" button actually doesn't display the word "use" [0].
In the materialize.css file you're using, the xl breakpoint for the grid system begins at min-width: 1201px , and there doesn't seem to be a consideration for higher resolutions than that.
If you wanted to fix this, since 1366x768 is a fairly common resolution on things like Chromebooks and older laptops (i.e. the computers your target market is somewhat likely to be using) you could just remove the xl2 CSS classes from the divs containing each of the buttons. This would display the buttons in three columns even on higher resolutions, enabling users to see the full button text.
That might look pretty mad on bigger screens though; you could also change "easy to use" to "simple" and that would probably also solve the problem — but that'd be cheating.
Personally, I'd add in my own xxl media query for higher resolution screens. Working with materialize.css's existing media queries, it would look something like this [1].
After adding that media query to the CSS file (after the others or it won't work), I'd then change the xl2 CSS classes to xxl2, leaving m4, so that it would display the buttons in three columns unless a high enough resolution is used that can display all the button text in six columns.
(Obviously, you could also use flexbox and it would solve the aforementioned issue as well, but I guess if there's a demographic that is likely to be using a browser that doesn't support flexbox, it's the elderly.)
[0]: https://i.imgur.com/uJJKHvz.png https://i.imgur.com/uJJKHvz.png
[1]: https://paste.sh/Axgmkd20#Q8zs4FfhQ_pbxrAzfUfSK9h8 https://paste.sh/Axgmkd20#Q8zs4FfhQ_pbxrAzfUfSK9h8
-------
Besides that, cool site. I have a question though: are you adding each device manually to your own database, or will you be getting the data from somewhere in the future?
I ask because I find it difficult to believe that I cannot purchase an iPhone SE in the UK, for instance.
- arnaudsm 9y agoThank you so much for the code ! I'm still new to Web Design, it's a big mistake for a lot of users indeed. I'm getting the data legally from fonoapi.freshpixl.com , but the Speed and Camera Scores are calculated with some Python wizardry. There's still a few prices missing, I'm adding the iPhone SE UK right now !
- wanda 9y agoNo problem, it's a cool project and I wish you the best of luck going forward.