Since last year's restructuring, the mailbox project has embarked on the road of pilot agile learning, even if there is a product plan entrusted to us, we have maintained agile internally as much as possible to keep up with changes. Before the final version is delivered, a small sprint is made every month to launch a full version of the new features that are available in time, which is the way to internetize the traditional craft.
After adopting the new development model, we have focused partly on requirements clarification and demand control, constantly screening the requirements and opinions gathered from various channels, and distributing them in each sprint after the decomposition of large functions, so as to quickly respond to users and ensure that the workload and manpower of each version match.
We have released several versions in succession, each of which is accompanied by new feature launches and experience optimizations, and here are some of the changes in recent releases.
Encoding error correction
Nowadays, there are many mail service providers, and there will always be some mail that is not coded according to the routine, such as the system mail of a domestic penguin manufacturer, which is displayed as follows after using outlook:
We have adapted to various scenarios as much as possible, so "common unconventional emails" are no longer garbled. But this can only be solved by one, so we have added some backhand tricks, such as the active encoding switching function, even if the encoding mark in the mail is wrong, it can be corrected by optional encoding. While incorrectly encoded messages or other possible errors have been stored in the past, we have added the ability to re-download messages to proactively resolve errors.
Mailing labels
I received some feedback before that the e-mail came with not enough stars. Recently, we have added the mail label function, you can add mail like adding a label to a friend on WeChat, so that you can see his classification when viewing the mail, and then you can also filter the mail that you have labeled in the label management window, so you don't have to create a special folder for individual special messages to manage.
Rich text editor upgrade
Because the email editing function is not powerful enough, especially the support for the table is not rich enough, we have comprehensively upgraded the write mail module, replacing the framework and plug-ins with the popular vue+tinymce, so the next functions of this module will be more and more rich, the user experience will be more and more friendly, and there are many interesting features to add. This time is also a lot of determination, because the replacement of the workload is very large, but agile we will not wait until the end to put out, we will be in a limited period of time gradually online, this phase of the version you can first experience the original tiny, but after two versions, you will see the deepin style editor is back, yes we still have to carry out magic changes :)
So the biggest challenge for us agile is not the acceleration of the pace, but how to cut a big function into a small function that can be released, respond to changes better than follow the plan, grasp the big and let go of the small, each cycle must have fresh functions online, otherwise, it can be bitter to the small partners in the community.
After agile, we have to do more planning, more waterfalls than in the past, each cycle has a complete requirements, development and version review, product Backlog in the large requirements also need to be reasonably disassembled according to manpower and cycle and even multiple lines of parallel development to achieve continuous "sprint".
For example, the rich text editor just now should be disassembled into a version of the framework with unchanged functions, a version with functional style adaptation, a version with new framework features added, and a final deepin version gradually online. And then the support of the Exchange protocol we will also support from the basic functions of the protocol first, so that everyone can experience it as soon as possible, followed by the gradual launch of the calendar and contact functions, followed by the support of CalDav, CardDav and Pst.
The motivation to embark on the path of agile still comes from being able to give quick feedback to everyone and constantly correct themselves. Of course, we also want to spit a groove, really hope to plan a window of our own spit, not good at any time can be "broken mouth scolding", scolding and scolding to find, hey, become better to use, instant black to powder haha...
We believe that the user is seen as multiple, in the user's mind there is a multiple, the improvement will be mentioned, the demand will be there, this is like bread and milk, to help the mailbox thrive, healthy on the road to agile.
More exciting, all in deepin20.5, welcome to experience!