愛奇藝知識移動端組件化探索和實踐

{"type":"doc","content":[{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"前言"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"組件化對於任何一個業務場景複雜的APP以及經過多次迭代之後的產品來說都是必經之路，組件化是指解耦複雜系統時將多個功能模塊拆分、重組的過程。組件化要做的不僅僅是表面上看到的模塊拆分解耦，其背後還有很多工作來支撐組件化的進行，例如結合業務特性的模塊拆分策略、模塊間的交互方式和構建系統等等。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"本文主要講述愛奇藝知識APP如何結合自身的業務特點，探索和實踐了一套高效的移動端組件化方案。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"01 背景與目標"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"1.1背景"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"愛奇藝知識目前有多個業務承載端，包括愛奇藝移動端APP的知識插件、愛奇藝iPad端APP的知識插件、隨刻移動端APP的知識插件和愛奇藝知識移動端獨立APP。由於各個端上線的時間不同，所承載的業務功能也不完全一致，造成了多端多套代碼的情況，維護成本很高。首先當相同或類似的功能需要迭代升級時，開發和測試都需要在多端同步進行，成本成指數級增長；其次隨着業務的快速發展，業務模塊在不斷增加，模塊間的依賴關係也變得越來越模糊，代碼耦合度和複雜度都在增大；另外在現有人力成本的基礎上如果想增加更多的業務端，就會變得非常困難。因此長期看非常不利於業務的高效迭代。下圖描述了組件化之前，愛奇藝知識各端的業務模塊架構。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.infoq.cn\/resource\/image\/41\/a4\/4166268c515e2ef6030e449d924caaa4.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":true,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}}]}