What is the idea of Mobile First approach?

Friends,

Now thinking of what a Mobile First approach actually, and all I could find online is:
  • You need to focus on the practices used when designing mobile interfaces (responsive design, degradation of the interface, working with text, etc.)
  • Need to design first, mobile design, and increasing the screen to develop the interface for desktops


In General, do not understand the difference with the usual adaptation for mobile devices when an interface is designed under the desktop, and then the interface degrades with decreasing screen size.

As if we did not move from the desktop to mobile devices, or Vice versa, in any case, we must ensure the quality and correct operation of the application, so no matter how we moved, in any case, the result should be identical.

Can anyone suggest what I missed, what is the result of this approach is different from others?
April 4th 20 at 00:37
3 answers
April 4th 20 at 00:39
Being able to do a small, to afford more simpler than having many, start to limit yourself.

The same long and in English. in post.
paragraph
Progressive Advancement has won the game for now as far as I can see. If UI/UX designers start a product design with its desktop version, they will inevitably want to make use of most of the advantages of the advanced end. For example, the hover effect which is supported by a mouse cursor; HD images & complex charts which can display normally only when there is a recent bandwidth. In this way, the designers will make efforts to complete an amazing desktop version and only to find it can hardly be adopted on a mobile end unless they give up a lot of beautiful ideas. If so, the mobile end version will be more like an an afterthought, an incomplete product which's been watered down.
April 4th 20 at 00:41

Need to design first, mobile design, and increasing the screen to develop the interface for desktops

In this case, you will have a limited field, thus you will think about a more compact and try to fit the actual.

In General, do not understand the difference with the usual adaptation for mobile devices when an interface is designed under the desktop, and then the interface degrades with decreasing screen size.

Previously did (and many still doing it), but because of the trend to "all at once", which was followed by the designers couldn't fit all that on a desktop in a mobile interface.

This "rule" just appeared in the background of the trend to "stuff"
April 4th 20 at 00:43
1. Mobile first implies a certain process of work closer to product development. It is important not to make all the screens at once, but gradually version version to roll out functionality. On mobile screens the functionality of the restricted device and on desktop screens it is wider.

Imagine what would happen if you start with the desktop screens: you design the interface, introducing there the entire desired functionality, roll out, and after a month realize that it is not feasible on mobile. It turns out that your design decisions from the outset are beginning to "accumulate error" all of this is revealed later and you make changes in ALL screens, plus it is still necessary to alter during the development phase, which is very expensive. If you use mobile first, then you complicate the interface of evolutionary, adding feature for feature, from the simple to the complex, and then, in the case of errors, roll back will just have to step back.

To sum up, it could go either way, really, especially if you work with a custom development, when you just "salesint" and give all the screens at once and forget. But in terms of product development, when the need to conserve resources, mobile first looks more efficient.

2. Probably more the fact that mobile traffic a few years ago exceeded desktop.

Find more questions by tags JavaScriptDesignAdaptive design