Where is the fat paper spring? Fat app tells you

  app is no longer the rhythm of individual combat, those small and beautiful app can continue to preempt the blue sea, while those all-inclusive APP The is more deeply responsive to the user's rigid needs. app applications need to provide more and more valuable services, not just in a small mobile screen, They need to solve the different size of the platform to adapt to the problem, it is necessary and brother app the formation of a common joint effort to provide users with services cluster. And with the continuous iterative iterative iterations, more and more functions, and finally, slowly become a fat app , so fat app and what happened to the changes, now what kind of transformation need to be made

This article will focus on the fat APP 's 4 big development Direction --1.app plugins 2.APP interoperability 3.APP Shell 4.APP Extensibility. This 4 orientation, while allowing fat clients to better meet user needs, can still maintain a good user experience of APP lightweight.

　　1.APP Plug-in

With the current version of the mobile app iteration, just the app, which meets the basic functionality, is bound to be somewhat frustrated on the development path, and the app can become bloated if more enhancements are to be made. So how do you balance the user's needs with the APP 's bloated ? An easy way to do this is to make the app plug-in, fatten the thin app , and slim down the Fat app , all based on user needs and choices.

eg. Baidu Cloud

Baidu's toolkit is such a plug-in means. You can put your address book, short MMS are back to the cloud, you can install online video playback plug-ins, image processing Plug-ins, and all of this is based on your needs to obtain. When you need to, authorized to install the appropriate plug-ins. This ensures that the app's functionality is complete and the installation package is small enough. There will not be too many distractions to disrupt the main task.

eg. micro-letter

The same is true of micro-letters, which are bound to make apps bloated as new features are added to the iteration. In order to make the product more lightweight, the micro-letter will be a number of unimportant functions hidden, the use of some of the features not commonly used as plug-ins, users can be selective installation. such as voice input, QQ mailbox reminders and so on. Only to the micro-letter 5.0 version, most of these plug-ins into the service number, such as QQ offline messages, QQ mailbox reminders, I think this is the micro-letter as far as possible from the SDK to the client form of the conversion into webapp this lightweight form of a transformation. At the same time, users do not need to understand the concept of plug-in technology, but when you need, you can get the corresponding services.

2.APP Interoperability

Single app is difficult to become a strong climate, and it is difficult to meet the increasingly complex depth of demand. and split into a number of sub app, you can borrow each other, you can flow with each other. Especially when two apps are in the downstream of the demand chain, it is very important to improve the user experience if you can call each other to solve certain requirements. The interoperability between apps, that is, the amount of app each other means, but also the user needs to meet the means.

eg. google++, photos, hangouts

Google products can form a promotional chain between each other, using their sidebar as a push resource. Google search from the home page can be clicked into Google +, from Google + 's sidebar, you can click on the album or ring chat, and from the side of the album, you can click again to tune up Google +.

This is the logical map of Google product intermodulation, you can see that Google products are in fact lack of a completely unified layout and thinking. Although the use of the jump between the app can bring a certain amount, but the intermodulation has to adjust the logic of the app, and the logic of switching labels, will lead to return logic is often confused. But it's already the best of the app-intermodulation approach.

eg. micro-letter, micro-vision

Micro-letters can invoke a variety of third-party apps, which combine a better case, is micro-letter call micro-vision, video and then share the process of micro-trust.

Micro-trust call micro-vision, is the middle Insert task stacking class of the plug-in process, once the call process is over, micro-vision also completed its mission. This invocation is done on a mission-by-task basis.

Intermodulation regardless of the amount, or to meet the needs, are very careful to deal with the return logic between the app, so as to allow users to experience the trip closed loop, to avoid the app switch produced a sense of fragmentation.

3.APP Shell-breaking

Every app is an island of information, and there's no way of knowing how much valuable information is in the app until the app is downloaded. and app download, installation, login cost is very high. Just think, you want to see a video, need more than 10 app one to search, want to read an ebook, also need to download more than 10 app one to find. So app shell retrieval is really a problem to solve. How can you quickly know what's in the app without installing the app? How can you quickly index the contents of an app with apps?

Google to solve this problem, the launch of the app Indexing,app indexing is also a Web site and app developers, it is a Web page and an app page, so now you search the Web is equivalent to search the content of the app, if the search, It displays an "Open in App" button. However, if you do not download the app, it will not display this button.

eg. Google search, Baidu app

Android platform system-level applications can be retrieved, such as Google search, you can search contact information, index to all applications, find the chrome browsing history, and so on. iOS platform is also, only the system-level app, can be better indexed to content, with Baidu app search for a contact, you can directly index to the address book. Other third-party apps, however, have trouble indexing the contents of the shell, which is a solution.

eg. Pea pods

The application of Pea pod search, but also with Google App index similar solution, the difference is that the Google App index is needed app matching Web page to achieve the search. The application of pea pods does not require web support. By indexing the content, and then the corresponding app to browse content, this is probably the most imaginative way to date, but completely break the island of app barrier, but also need more apps to support the application search.

4.APP Extensibility

With the passage of time, the major manufacturers of continuous iterations, more and more platforms, more diverse resolution, historical version of more and more, maintenance costs and adaptation costs are increasingly high. To do this it is necessary to fully consider the scalability of the app when developing versions. Can the app be compatible with a variety of resolutions, and can a design fit multiple platforms?

eg. Google now

Google Now is the best case for scalability, not just for mobile-end platforms, but Google Now Glass, Android Wear seems to be easy, and even now the form of voice interaction seems to be designed to be considered wearable.

eg. Baidu Cloud

Baidu's Android version, iphone version, PC version, Mac version, TV version of the launch, if not to consider the expansion of the design and product team will be devastated. At present, to do the design framework, are the greatest degree of consideration of the full platform scalability, and even in the future to wear the market fit. The app features a lot but the structure is still simple to maintain.

Finally let us review, Fat app development, will certainly become the user's burden, so we have to consider Fat app slimming, or Fat app split, mainly refer to the manual--1.app plug-in, 2.APP interoperability 3.APP shell 4.APP expansion. These 4 directions, can let the fat client better satisfy the user needs while, still can maintain the light quantification good user experience.