"App development" published

The ancient people of wealth and name out, not to win remember, only suave very person Yan. Therefore Hebrew detained and played "Zhouyi", Qu Yuan exile, is Fu "Li Sao". The literati and the Bards sublime, and I can not mundane, but also to arty, write a Before the ancients, not see the classics.

So, lasted a year, painstaking, combined with their own 3 years of experience in the field of application, and then supplemented by more than 10 in the software industry artifice, write down this voluminous 300 pages a hundred thousand of words. After the first draft was finished, it was as if I could not find a publisher who was willing to publish, and I refused to compromise to write introductory chapters such as grammar and UI layouts. At this time, Du helped me introduce the mechanical industry publishing house Wu Yi Teacher, contributed to the publication of this book.

Near publication, Zhou Hongyi and Liu Jiang, Mi Yimin and other people's preface. Liu Jiang is the guide who brought me into the book publishing, and in retrospect it was eight years ago, and Mi Yimin was the inventor of Waxpatch, the first person in the world to fix the bug on the iOS hot fix line (Jspatch a few years later). Speaking of Zhou Hongyi, that was my mistake in a certain group to know, he appreciated my way to the black research spirit, and I appreciate his personality publicity. In reality we have never met, a few days ago I went to 360 to send him the sample booklet, security do not let in, I had to drubbing and return.

Book Address: http://item.jd.com/11791229.html

With the book Source: http://www.cnblogs.com/Jax/p/4656789.html

Finally, attach the preface to this book, readers:

Spectacular 30, book sword two underachievement

Instilled in front of you, I used to be a technical otaku. I have been writing technical blogs for more than 6 years and more than 500 technical articles. Ten years of programming career, I studied. NET all the technology, but from Microsoft out, set foot on the Internet this road, but found oneself still is elementary school level, at that time coincides with 30 had been, feeling oneself for many years to accomplish nothing, therefore began a new round of study. Choose the direction of mobile Internet, because everyone in this field is from scratch, we are groping to do, the initial high and low points.

During this time, I did the Windows Phone app, learned Android and iOS, slowly from two knife level to upgrade to today's books were written, originally I wanted to write the iOS framework design, because there will be more experience in this area, I wrote a series of articles on the blog in 2013, but I didn't finish it. Today the book is based on Android, but the idea of frame design is consistent with iOS.

As a programmer, do not write a book circulated in the world, seemingly sorry for this profession. 2008 I wanted to write, but at that time accumulation is not enough, the knowledge will be more from the book to see, so did not dare to pen, but chose to translate a book, "MSIL authoritative guide." I can only honestly translate in accordance with the original, but not to play. I am eager to have a place, unrestrained to my style vividly show, before writing this book, only my technical blog.

Finally gave himself an account, East has died, Sangofi.

Article this day, hands even

This is a very different style of the book, so that after the completion of the book, I do not know what to give a title. I just hope that the readers can get some revelation after reading it, and I am satisfied.

Here's a summary of the chapters in this book. The book is divided into three sections totaling 12 chapters.

The 1th chapter is about refactoring. This is the basis for follow-up Chapter 3. Before you look at the other chapters, take a look at what this chapter describes and whether your project has been done.

The 2nd chapter is about the network bottom package. Each company encapsulates the app's network communications, but it is slightly bloated. The network framework I introduced is smart and free of asynctask, and can quickly extend new functionality at the bottom or top. So how much some puff, good or to listen to the reader's feedback, recommend the use of new apps.

The 3rd chapter introduces some classic scene designs in the app, such as the incremental update of the city list, the design of the cache, the interaction between the app and HTML5, and the use of global variables. Do the readers have a sense of déjà vu about these scenes and can they resonate with my solution?

The 4th chapter describes the Android naming conventions and coding specifications. The various specifications on the Internet are numerous, but we can not directly take to use, to have a critical succession of absorption, to summarize the norms for their own team. Therefore, even if this chapter of my content, I also ask you to choose to adopt the reader. The purpose of my writing this chapter is to emphasize "no rules inadequate surrounding area", and the code is also.

Chapters 5th and 6th make up the Android Crash Analysis trilogy. It took me a year to write this book, which was spent more than six months on the two chapters. On the one hand, to constantly optimize their own algorithms, training machines to classify crashes, on the other hand, it is more than 80 kinds of online crashes traced to find the real reason.

The 7th chapter is about confusing code in Android. Should not have this chapter, only in the work found online about Proguard most of the words. The official has a white paper, but the introduction to Android is not a lot, so wrote this chapter, systematically and comprehensively introduced the use of Proguard in Android theory and practice.

The 8th chapter is about continuous integration (CI). 10 years of experience in traditional software makes me handy in this area. What this chapter solves is how to move traditional software ideas to apps.

The 9th chapter is about the app competitor analysis, which is a study of dozens of famous apps on the market and a lot of technical articles. I've had more than 10 years of experience in software development, which helped me tremendously.

The 10th chapter is about project management, which is an agile process tailored to the app, and is the development model that I have been using in my team. The app typically releases 2 weeks, and the iteration cycle is very fast, and is suitable for agile development models.

The 11th chapter is about the problem solving in the daily work. It was the method that was summed up in the days of licking blood on a tip, when every day was spent in trepidation, and there was a problem to find the cause and fix it as soon as possible; it is also the fastest time for personal empowerment, and every successful problem solving is accompanied by personal growth.

The 12th chapter is about app team building. I am a peacock character boss, so my team is mostly export-oriented people, or, the various types of stuffy technology otaku into the Ming Sao; I came out of the technical community, so I will promote technology sharing, care about the growth of everyone; I have 8 years of experience in software companies, so I am good at writing documents, drawing flowcharts, To make sure everything is under control. There is such a wonderful flower boss, the opposite of you, not fast to my bowl, my mailbox is [email protected], my team, look forward to your joining.

The heart is like a tiger, the Rose is fine

In other words, I have inadvertently embarked on the path of programming. I may be a mathematician now, or as much as my classmates do, or the two-class market, if I am not really learning to understand the course of real variable functions.

My real hobby is reading books, the first is to govern Tong Jian, histories, and later found in the table said these will be the younger sister as monsters, so according to the suggestions of Chinese students look at Zhang ailing, Wang Xiaobo novels, read Liang Shiqiu essays. In Fudan four years, smoked out a "smelly problem", for example, watching the night sky in the moon will somehow shed tears, will like to drink milk tea and picky taste of pearls.

Don't assume that programmers will only write code. Programmers do baking is absolutely inverse, because it is used in software design patterns, I also developed a failure of dessert, making biscuits when the butter was mistakenly used as a light cream, and then the baking of the biscuit the next day to the workers to eat.

I am involved in a lot of fields, such as cooking coffee, singing K, watching old movies, are in the programming technology to a certain bottleneck after learning, each kind has a deep knowledge. Do not look at the code mindedly, life can teach us a lot, and then in turn let us have a deeper understanding of programming.

If the heart has Taoyuan, where is not the water cloud between.

When the Ling, at a glance at the mountain small

If there is a second volume, I would like to talk about data-driven products. During the writing of this book, my mind had a sublimation, which was a snowy night in the early 2015, and I completed the shift from a tangled approach to writing code to a data-driven product. This is also the book in front of a lot of code, the more the code behind the less reason.

Data-driven products are the strategic layout of the next decade. Before, we pay too much attention to the method of writing code, but always do not know whether users are willing to pay for our hard-earned products, technical personnel do not understand, product personnel do not know. Product personnel need technical staff to provide tools to help them with the analysis, such as abtest, such as precision push platform, such as user portrait, and we check our own code, but found that even PV and UV can not ensure accurate.

This is my next research and work direction.

"App development" published