What do I do?
I’ve been a front end development siege lion on the front line, and a server in between, for a total of almost three years. As a technician, although the technology used in my work is limited, and I will not blindly pursue new technology, especially for companies with a long time, I still often pay attention to various novel technical frameworks and technical highlights. While lamenting the increasing number of technical frameworks and faster technological innovation, I also feel comfortable for our front-end development. The front-end technology has been very different from the previous front-end, and the front-end technology can do more and more things, and the way out of the front-end developers are more and more extensive.
Two, the first knowledge fast application: really so good?
Speaking of, the first to know fast application but not my own browsing blogs, forums, product understanding, but the company to push fast application version of the product. On the one hand, the domestic Android user group is large, which is directly based on the mobile phones of the top ten manufacturers and has large traffic. On the other hand, the experience is much better than the H5 and native version, the underlying capabilities are strong, the development cost is not much, the most important thing is that the number of apps in the quick app market at that time is not many, we can take this opportunity to push our product. So I was like, “Is it really that bad?” The mood to start learning about fast apps.
Third, Hello World
In fact, the previous good is the opinion of our product and marketing colleagues, I immediately began to learn fast application, went to check the official documents, and made the first fast application Demo. First of all, the first feeling:
The upside
- MVVM mode is very handy, for familiar with Vue. Js development of children’s shoes, learning costs are relatively small, is the label slightly different.
- Support async/await writing will solve the callback hell problem to a large extent, this is a great convenience for ES6, ES7 writing children, do not have to tangle with the complex client business.
- Compatibility issues: While there were occasional issues with a specific vendor during the development process, compatibility issues were far fewer than in the H5 development.
- Rich APIS: Not all of them, but when I saw the rich apis in the official documentation, I couldn’t help but marvel that the underlying capabilities of Kuaiapp are much better than those of other similar products, and are directly based on android phone manufacturers, so I don’t need to worry about some permissions being disabled one day.
- Support Less, front-end development may have experience, after writing Less or Sass, do not want to write ordinary CSS, because the former ability is stronger, code readability is also stronger, more standard and systematic, so fast application support Less this is really quite convenient.
The bad side
In fact, it can not be regarded as a bad aspect, maybe SOME of my own development is not used to it:
- Flex layout: I have been doing Android development for over half a year. The Flex layout on the front end is similar to the Android layout, which is actually very, very convenient, but using flex layout completely is still a little uncomfortable.
- It doesn’t preview in real time, and while watch mode can listen for changes and restart apps in real time (a ‘refresh only’ feature was added in later versions), it’s still quite inconvenient.
- Breakpoint debugging is not supported: since version 1020, breakpoint debugging is supported, but debugging is done in compiled JS. It often freezes, and it is not convenient to always output logs to debug.
Four,
Overall, my first impressions of fast apps are very good, and as I said at the beginning, for a front-end developer, there is more and more that front-end technology can do and front-end developers can do, which is a very good thing. At the time of writing this article, the company has launched two quick application products. I will share with you the problems I encountered in the actual product development and the solutions in the following paragraphs. If there are mistakes, please do not hesitate to correct ~