New answers tagged

0

In my opinion, this is an accessibility issue. Should you design for a viewport width of 320px, probably not because market share for that size is very low. Should you make sure it renders properly and is usable at 320, absolutely!


0

First of all, this looks very complicated for registering to the event. Can you remove some of the required fields. Challenge the absolute minimum amount of needed information entry and steps. Why do you need something else than than picking an event and entering your email address? Secondly the navigation seems odd, there is double navigation (hambuger ...


0

A - This is the preferred option. That said, the content has to be crystal clear, both before and after the selections are made as this ensures that the user is informed and doesn't leave the process thinking that they were successful in getting everything they selected. The user first needs to be informed that there is no guarantee that every selection ...


0

According to you, what you made was a landing page. So generally designing based on breakpoints is your best bet. Breakpoints are the point at which the content of your site will respond to provide the user with the best possible layout to consume the information. So say your initial desktop width was 1440px, and your mobile is now 360px. Those are the ...


0

From a technical standpoint, assuming this is a web application, I feel this would be easily fixed with a max-width: 100vw. It looks like you need to restrict the width of the iframe to match the viewport and also need to remove any margin/padding so it spans the full width. The iframe itself should handle any scrolling required to view overflowing content ...


0

The difference between 375px and 320px is really not that much: it sounds to me like your design isn't truly responsive and is purely using fixed breakpoints. I have yet to find a situation in which my UI would not scale to fit on the smallest screen sizes assuming once I reached the mobile breakpoint I treat everything as a single full width column rather ...


0

Only 1%-1.5% of our users utilize a screen width less than 360. That's a lot of energy wasted to design for 320 when the number of users is so low. That's not a good ROI.


1

Is it a web app or a mobile app? Either way, on mobile phones in portrait orientation it is abnormal and inconsiderate to reserve so much screen real estate for a fixed menu. In landscape it might work, but generally and as James Coyle says, a side-navigation can typically be hidden from view with a toggle. Tabs and Bottom Navigation work well in portrait ...


Top 50 recent answers are included