Have you really considered the implementation of the front-end for html5 design? (recently, some people often ask me this question, so I wrote this article, maybe someone else spoke like me), html5 front-end engineer
A long time ago, I was interested in HTML5 in Android 2.0! Because at that time, I just made a front-end entry. At that time, the greatest pleasure was to look at the effects of various css3 on w3plus. I felt that wow, I could have done this, and three years later... No 40 or 30 apps have been completed! Then, I attended the HTML5 summit last year. Listen to a group of elders who talked about the setbacks, experiences, and popular frameworks they encountered on the html5 road to create HTML5 ide... It's also a little experienced !... Then, the more you know, the more cruel the reality is. (Desert said that he could not JS, even the idol once said that he would not actually js and swear! This is so crazy) and then let it go. Now (reality is at your feet ...)
Now, my friends, our former friends and designers have all said that they are starting to develop apps. HTML5 is coming soon.
Then-_-// I just want to tell you what you know about HTML5!
1... a beautiful designer who just left said: they are now using apps and H5. They want to design H5 pages. I have to vomit! Are you sure you are not in the trap of designing the page !.... They are all art words! Are you going to let the front end use canvas and load the font? Is this font a hand-drawn image .. (In their eyes, html5 may be something that frees them from considering compatibility and can give full play to their inspiration.) But have they considered the image weight and introduced the font library size! Even if it is finally packaged into a mobile APP! Is this really suitable! If it is only a webapp, he thought that if users are not using wifi, it will cause a lot of traffic waste on loading pictures and fonts. Finally, if the front-end is very high, they can use linear-gradient to make a lot. the results of those tall pages at the bottom of this page. However, I have to pour the cold water again. Only the safari browser, that is, the fruit, is completely compatible with Android4.0 (at least Android 4.0 is not fully compatible )... Last question!
I just want to say that when the front-end is trying to reduce the size of the Code, even if it is 20 K, Can designers take into account all the images you have made, can it reduce the point volume?
After all, what you do is a product APP. No one has taken the initiative to launch it, except for your customers! Of course, if your product can reach others, even if it is burned for 2 MB, you can open your page or go offline once.
Store 20 mb of images. There is nothing to say.2 ..... A pretty designer asked: how to design a standard mobile terminal, how do front-end engineers implement it? Generally, there are about three types of webapps. The first is Sina-like web pages... Brainless full screen width: 100%, on the computer or 100% second similar to the micro Shop Network ..... Maximum Width: 680px ..... you can download the mobile phone client of weidian network. The page is opened on the 680 page (the main spring festival shakes more than 20 yuan of red packets, so the next one). The third response layout (the most accurate) the designer needs to prepare three resolutions, open a page, and adapt to the screen width (such as bootstrap). The rest is either magical or funny, and I will not list them.
Generally, you need to design a 680-width cluster.3 .... a small white front-end asks (px in design) What font units should I use ..... Not qualitative! But most officials like EM... However, the usage of PX is more accurate.
4 ...... I have to vomit ...... do not randomly design the effect of the left and right landscape screen for a mobile phone webpage
Note keywordsWebpageThe key to this problem is that the Left and Right landscape screens have disastrous consequences on the webpage! For example, the mobile browser moves to the left to the right, causing the mobile browser to move forward and backward !!!
I don't have to worry about packaging! After all, phonegap and appcan must have sufficient support for this problem.