Some time ago, there was a rare war between Xiaobian and our mobile product manager.
(Seeing the word tearing force, it is estimated that readers and friends are excited, hehehe...)
The reason for this is this. Based on the understanding of customer needs and peer products, the editor made a post about the adaptive display of reports on various screens.
(Original link: http://bbs.finereport.com/thread-74232-1-1.html )
The editor who finished the post felt as crazy and cool as the title he gave to the post at that time.
However, the brilliance that blows out is like water that is poured out, and one day it will be poured back and splashed all over itself.
No, within a few days, the editor was slapped in the face.
Not by the customer, nor by a friend, but by his own people! ! !
Jane, our mobile product manager, also made a post, bluntly, saying that there are some pitfalls in the user experience of the adaptive form on the mobile phone.
(Original link: http://bbs.finereport.com/thread-74325-1-1.html )
After reading the post, my first reaction was this.
Calm like me, wise like me, the second reaction is like this.
Isn't that what a good product manager should be like? !
It is not only necessary to lead the product to occupy the leading position in the industry, but also to stay awake to the reality at all times!
Thinking of this, the editor can't help but give a thumbs up to Jane's self-reflection courage!
With the efforts of product manager Jane and more programmer colleagues, FanRuan's mobile reports are not perfect at this stage, but they already have quite complete functions.
Not only can you conveniently view reports on mobile devices, you can also fill in data, and support filling and viewing offline (off-line) conditions;
There are also powerful experiences such as annotation, sharing, message push, and WeChat reports.
Just to give you two screenshots of the report on the mobile phone:
However, in not all cases, you can experience the functions of FanRuan's mobile terminal perfectly, especially when the report needs to be integrated with a third-party APP.
Since FanRuan's mobile reports are divided into two types: native parsing and HTML5 parsing, different methods will have different functional experience.
Under what circumstances do you use native? When to use HTML5? What are the current differences between the two?
In view of the fact that many friends are confused about this piece, our product manager Jane Children's Shoes specially instructed the editor to explain it to everyone in a vivid, vivid, realistic and radiant way.
Vivid and radiant? Hehe, the image of the editor has always been brilliant! Aren't my writings always vivid!
Wonderful pen makes flowers, the best at it! The editor will show you the similarities and differences between native reports and H5 reports in minutes today.
Oh, I really vomit blood, can I still play happily? Why does the family bully the family?
The editor secretly tells you that although there are many functions that are inferior to native reports, H5 reports are naturally developed for WeChat and DingTalk, and they are integrated well.
Another spoiler, H5 support for forms is expected to be available in the June version.
Although the native report currently does not support the new feature graphics, the existing old charts are also great, and the adaptation of the new feature charts is also underway, and the time is also in June.
In addition to the above differences, the treatment of H5 reports in other aspects is almost the same as that of native reports.
The above is a comparison of some differences between native reports and H5 reports. The functional experience has its own advantages and disadvantages, and the native report currently has the upper hand.
In terms of operational difficulty of integration, H5 reports are relatively easier: H5 integration is mainly for single sign-on, while native report integration requires importing SDK and subsequent update and maintenance.
Finally, through a table, I will sort it out for you.
