Set off
After many rounds of APP development/testing/launching/operation cycles, we feel that the APP bug feedback link is always very inefficient, and we have to change this state. Hence the bugtags.com .
one year
It has been almost a year since the official launch of the project in June last year, the internal test in mid-August, and the official launch in mid-September.
I still remember that in mid-August last year, we were nervous and sent it to our friends to try it out. Unexpectedly, the praise continued. The invitation code application mechanism set up at the beginning was forced to cancel within a few days-because too many people applied, it was handled. But come.
The happiest thing for people who make products or technologies is that tens of thousands of people use their products. At Bugtags, we enjoy such happiness every day.
product
Internally, we use Bugtags for process management, which is the so-called eat our own dog food, when using our own products, we can find many problems.
Bugtags are constantly evolving, fixing some early bugs, adding some functions that make the product complete, and adding some new functions, such as 网络监控、测试用例、实时调试etc.
When adding features, we always remember part of our original intention for creating Bugtags: products like JIRA are too heavy and complicated! We're also constantly asking ourselves: Are we turning Bugtags into the kind of product we've been lashing out at?
We are always careful to improve the product, adding features but putting it in the right place, polishing the user experience in the details.
Technology
In the early days of the product launch, we received a lot of user feedback every day, mainly on integration issues, SDK compatibility issues, etc. We will always lie on the group and solve it as soon as possible. Since this year, most of the questions have been sorted out and answered. In the process of answering this question, our understanding of the system is also deepening.
Since the Spring Festival, as the number of users increased, the pressure on the server continued to increase, and finally on a weekend, the service was almost unavailable. Our backend team used a variety of combinations to hold the traffic. Really feel it 没有经过流量冲刷的后端，那不叫好后端.
We are always using mainstream technologies in the industry and embracing open source. When the open source system does not meet the requirements, it will customize some modules by itself.
team
Our core team has been working together for a long time, and everyone's role is clear. As the person in charge of technology, I myself have to undertake heavier development tasks. To be honest, I don't have much time for management. This requires that everyone on our team is highly self-driven and knows what to do and how to do it well. In fact, each of us is like this.
We insisted on the stand-up meeting every morning, with the aim of transparency of information and early exposure of problems.
Whenever a user praises our product for doing well, we will take a screenshot and put it in the group, so that everyone in the team can feel the glory. The user's praise belongs to everyone.
Every new member of the team, I will interview, in addition to business ability, I will also emphasize the culture of our team: 用户为中心的态度，积极快速做事的风格.
In the last two weeks of June, our small team realized the rapid launch of the real-time debugging function, which fully reflects our combat effectiveness.
future
Since April this year, we have launched a paid version. So far, we are quite satisfied with the results. This further strengthens our drive to continue to innovate and strengthen user services.
We're among them this evening in a white paper on the Enterprise SaaS Marketplace by Jigsaw Business Review . In fact, this is beyond our expectations.
This year, we have hardly done much promotion, so far, 类似大疆无人机这类独角兽公司，新浪、网易、Microstrategy 等这类上市公司，以及各行各业数万家企业都在使用我们的产品，甚至有业界某些大公司，在像素级学习我们的产品.
In any case, we are very happy to be recognized by the industry.
With the deepening of the product, we found that there are still many points that can be deeply digged. This is how entrepreneurship is, continuous innovation, adjustment of direction, persistence, and cycle.
In the next year, we hope to continue to strengthen the brand, making it possible to reach more users.
We hope to launch more and more powerful practical services to help developers better develop, test, launch, and operate.
Let's look forward to the future together!