[{"data":1,"prerenderedAt":598},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-app-revamp-takeover-guide":106,"article-related-zh-tw-app-revamp-takeover-guide":583},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":551,"cover":552,"dateModified":553,"description":554,"extension":555,"faq":553,"hasCoverTitle":556,"locale":557,"meta":558,"navigation":559,"need":560,"path":561,"seo":562,"seoDescription":553,"seoTitle":553,"sources":563,"stem":573,"takeaways":574,"time":580,"type":581,"__hash__":582},"content\u002Fzh-tw\u002Farticle\u002Fapp-revamp-takeover-guide.md","APP 改版與接手：改版前要盤點什麼、誰來維運、要不要做 Design System",{"type":110,"value":111,"toc":532},"minimark",[112,116,119,122,127,130,197,206,210,213,254,264,268,271,303,318,322,325,374,388,392,395,398,459,467,471,474,486,489,494,497,501,504,508,511,515,518,522,525,529],[113,114,115],"p",{},"APP 要改版或換團隊接手，第一步是盤點，不是重畫畫面。原始碼、開發者帳號、簽署金鑰、後台與伺服器權限都確認拿得到，新團隊也能自己重新打包上架之後，才開始改功能；改版後誰來維運、要不要做 Design System，也要在開工前決定。",[113,117,118],{},"會來找人改版或接手的 APP，通常是這幾種情況：原本的開發商不再維護、內部工程師離職、畫面和流程舊到使用者抱怨，或是幾支 APP 要整併成一支。不管哪一種，順序都差不多：先把東西拿齊、確認能上架，再談改什麼。",[120,121],"article-cta",{},[123,124,126],"h2",{"id":125},"app-該小改大改版重寫還是換團隊接手","APP 該小改、大改版、重寫，還是換團隊接手？",[113,128,129],{},"看兩件事：現有程式碼還能不能安全地改，以及問題出在介面還是底層。介面舊但程式碼健康，做改版就好；程式碼沒人看得懂、套件太舊無法更新，才考慮重寫；原團隊無法繼續時，先接手穩定下來，再決定改版或重寫。",[131,132,133,149],"table",{},[134,135,136],"thead",{},[137,138,139,143,146],"tr",{},[140,141,142],"th",{},"做法",[140,144,145],{},"適用情況",[140,147,148],{},"開工前要先確認",[150,151,152,164,175,186],"tbody",{},[137,153,154,158,161],{},[155,156,157],"td",{},"小改版",[155,159,160],{},"流程大致可用，只是畫面老舊或少幾個功能",[155,162,163],{},"原始碼能編譯、能上架新版本",[137,165,166,169,172],{},[155,167,168],{},"大改版",[155,170,171],{},"使用者流程要重新設計，或要整併多支 APP",[155,173,174],{},"後台與 API 能不能沿用、資料怎麼搬",[137,176,177,180,183],{},[155,178,179],{},"重寫",[155,181,182],{},"技術太舊無法符合商店規定，或程式碼無法安全修改",[155,184,185],{},"舊 APP 的商業規則有沒有人說得清楚",[137,187,188,191,194],{},[155,189,190],{},"換團隊接手",[155,192,193],{},"原開發商不再維護、內部工程師離職",[155,195,196],{},"原始碼、帳號、金鑰與伺服器權限是否齊全",[113,198,199,200,205],{},"重寫聽起來最乾淨，但要重新理解舊規則、搬資料、雙軌驗證，成本常被低估。如果是整個系統都沒人能維護，可以先看 ",[201,202,204],"a",{"href":203},"\u002Farticle\u002Flegacy-system-takeover-guide\u002F","舊系統接手指南","，裡面有健檢與重構、重寫的判斷方式。",[123,207,209],{"id":208},"改版或接手前要盤點哪些東西","改版或接手前要盤點哪些東西？",[113,211,212],{},"要盤點六類：原始碼、開發者帳號、簽署金鑰與憑證、後台與伺服器、第三方服務、文件與數據。其中帳號和金鑰最容易出問題，少了它們，APP 就算改好也上不了架。",[214,215,216,224,230,236,242,248],"ol",{},[217,218,219,223],"li",{},[220,221,222],"strong",{},"原始碼與版本庫","：iOS、Android、後台與 API 的完整原始碼，包含目前線上版本對應的那一份，不是某個舊的備份。",[217,225,226,229],{},[220,227,228],{},"開發者帳號","：Apple Developer 與 Google Play Console 的帳號在誰名下、誰有管理權限。",[217,231,232,235],{},[220,233,234],{},"簽署金鑰與憑證","：Android 的上傳金鑰、是否使用 Play 應用程式簽署；iOS 的推播憑證或金鑰。",[217,237,238,241],{},[220,239,240],{},"後台與伺服器","：主機、資料庫、網域、雲端帳號的管理權限，以及部署的方式。",[217,243,244,247],{},[220,245,246],{},"第三方服務","：推播、金流、地圖、簡訊、分析工具的帳號與合約在誰名下。",[217,249,250,253],{},[220,251,252],{},"文件與數據","：API 文件、商業規則說明、使用者回饋、閃退紀錄與使用數據。",[113,255,256,257,263],{},"Android 的簽署金鑰要特別注意。Google 說明，使用 Play 應用程式簽署 時，上傳金鑰遺失可以申請重設；但自行保管的應用程式簽署金鑰一旦遺失就無法重設（",[201,258,262],{"href":259,"rel":260},"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F9842756",[261],"nofollow","使用 Play 應用程式簽署","）。接手前先確認這一點，能省掉很多麻煩。",[123,265,267],{"id":266},"上線中的-app-怎麼接手服務才不會中斷","上線中的 APP 怎麼接手，服務才不會中斷？",[113,269,270],{},"先證明新團隊能自己重新打包、上架一個不改功能的小版本，再開始改東西。這一步確認了原始碼、帳號與金鑰都是對的，之後的改版才有安全的起點。",[214,272,273,279,285,291,297],{},[217,274,275,278],{},[220,276,277],{},"盤點與交接","：照上一節的清單收齊，缺的項目列出來，和原廠或內部窗口一起補。",[217,280,281,284],{},[220,282,283],{},"建立可重複的建置環境","：在新團隊的環境重新編譯，確認產出的 APP 和線上版本行為一致。",[217,286,287,290],{},[220,288,289],{},"上架一個小版本","：只修小問題或更新套件，走一次完整的送審與發布。",[217,292,293,296],{},[220,294,295],{},"掃描與補強","：交付前自行完成原碼掃描與弱點掃描；需要黑箱測試時由第三方執行，JoinX 可以協助聯繫，修補弱點後再交付。",[217,298,299,302],{},[220,300,301],{},"開始改版","：依優先順序分版上線，每一版都留回退的方法。",[113,304,305,306,311,312,317],{},"開發者帳號如果不在你們公司名下，Apple 與 Google 都有在開發者帳號之間移轉 APP 的流程。Apple 說明，移轉後 APP 保留評分與評論、使用者繼續收到更新（",[201,307,310],{"href":308,"rel":309},"https:\u002F\u002Fdeveloper.apple.com\u002Fhelp\u002Fapp-store-connect\u002Ftransfer-an-app\u002Foverview-of-app-transfer\u002F",[261],"Overview of app transfer","）；Google Play 也有對應的 ",[201,313,316],{"href":314,"rel":315},"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F6230247",[261],"移轉流程","。換團隊時順便把帳號移回自己名下，下次就不會再卡住。",[123,319,321],{"id":320},"改版後誰來維運","改版後誰來維運？",[113,323,324],{},"三種常見做法：內部團隊自己維運、交給外部團隊維運，或內部負責需求與驗收、外部負責開發與維運。不管哪一種，合約要寫清楚維運範圍、支援時段、回應時間，以及原始碼與帳號在誰名下。",[131,326,327,339],{},[134,328,329],{},[137,330,331,333,336],{},[140,332,142],{},[140,334,335],{},"適合誰",[140,337,338],{},"要注意的地方",[150,340,341,352,363],{},[137,342,343,346,349],{},[155,344,345],{},"內部團隊",[155,347,348],{},"已有 iOS、Android 與後端工程師的公司",[155,350,351],{},"人員異動時的交接文件",[137,353,354,357,360],{},[155,355,356],{},"外部團隊",[155,358,359],{},"沒有內部工程團隊，或 APP 不是核心業務",[155,361,362],{},"原始碼與帳號保留在自己名下",[137,364,365,368,371],{},[155,366,367],{},"混合",[155,369,370],{},"內部有產品負責人，開發量時多時少",[155,372,373],{},"需求與驗收的窗口要固定",[113,375,376,377,382,383,387],{},"維運不是「壞了再修」。iOS、Android 每年都有大版本更新；Google Play 從 2026 年 8 月 31 日起，新 APP 與更新都要以 Android 16（API 等級 36）為目標版本才能送審（",[201,378,381],{"href":379,"rel":380},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Frequirements\u002Ftarget-sdk",[261],"Android Developers 說明","）。沒人追這些規定，APP 某天就會發現送不了審。維運預算怎麼抓，可以參考 ",[201,384,386],{"href":385},"\u002Farticle\u002Fapp-development-cost-2026\u002F","APP 開發費用"," 一文。",[123,389,391],{"id":390},"改版要不要順便做-design-system","改版要不要順便做 Design System？",[113,393,394],{},"看產品數量和改版頻率。同時有多支 APP、網站要維持一致，或每季都在改版的，值得做完整的 Design System；只有一支功能單純的 APP，先整理基本的色彩、字級與元件規範就夠了。",[113,396,397],{},"Design System（設計系統）是把色彩、字級、間距與元件整理成一套共用的規範與元件庫。它的價值在後續：新增功能或延伸到其他平台時，直接沿用同一套元件，介面保持一致，也不必每次重新設計。",[131,399,400,413],{},[134,401,402],{},[137,403,404,407,410],{},[140,405,406],{},"情況",[140,408,409],{},"建議",[140,411,412],{},"原因",[150,414,415,426,437,448],{},[137,416,417,420,423],{},[155,418,419],{},"一支 APP、功能單純、改版少",[155,421,422],{},"基本 UI 規範",[155,424,425],{},"完整設計系統的建置成本回收不了",[137,427,428,431,434],{},[155,429,430],{},"一支 APP、持續改版",[155,432,433],{},"從常用元件開始，逐步擴充",[155,435,436],{},"改版越多次，共用元件省下的工越多",[137,438,439,442,445],{},[155,440,441],{},"多支 APP 或 APP 加網站",[155,443,444],{},"完整 Design System",[155,446,447],{},"跨產品維持一致，整併時也有共同基礎",[137,449,450,453,456],{},[155,451,452],{},"要整併多支 APP",[155,454,455],{},"整併前先建立",[155,457,458],{},"先統一元件與規範，整併時才不會各做各的",[113,460,461,462,466],{},"UI\u002FUX 與設計系統的做法可以參考 ",[201,463,465],{"href":464},"\u002Fdevelopment\u002Fui-ux\u002F","UI\u002FUX 設計服務","。",[123,468,470],{"id":469},"joinx-怎麼做-app-改版與接手","JoinX 怎麼做 APP 改版與接手？",[113,472,473],{},"我們接手過 100 個以上別人開發的專案，做法就是前面的順序：先盤點原始碼、商店帳號、憑證與伺服器權限，確認能重新上架，再開始改版，結案時交付完整原始碼與部署文件。",[113,475,476,477,481,482,466],{},"APP 方面，我們做過中華汽車車主 APP 的系統整併，也負責 ",[201,478,480],{"href":479},"\u002Fcase-studies\u002Fcapital\u002F","群益投信"," 官網、ETF 網站與 APP 的委外開發與維運。更多 APP 開發與維運的做法，可以看 ",[201,483,485],{"href":484},"\u002Fdevelopment\u002Fapp\u002F","APP 開發服務",[123,487,488],{"id":488},"常見問題",[490,491,493],"h3",{"id":492},"沒有原始碼可以接手-app-嗎","沒有原始碼可以接手 APP 嗎？",[113,495,496],{},"要先確認能不能從原廠、版本庫或備份取得原始碼與合法權利。只有上架的安裝檔、沒有原始碼時，通常無法安全修改原功能，比較實際的做法是規劃重寫。",[490,498,500],{"id":499},"換廠商之後app-要重新上架嗎","換廠商之後，APP 要重新上架嗎？",[113,502,503],{},"不用。只要拿得到原始碼、開發者帳號權限與簽署金鑰，新團隊就能沿用原本的 APP 送出更新，評分和下載紀錄都會保留。帳號不在你們名下時，可以走 Apple 與 Google 的移轉流程。",[490,505,507],{"id":506},"app-改版要多少錢","APP 改版要多少錢？",[113,509,510],{},"看範圍。接手前的初步程式與系統健檢常見約 NT$5 萬至 20 萬；之後的改版依功能拆項估價，可以參考 APP 開發費用的分級區間。重寫等同重新開發一支 APP，要依新範圍估價。",[490,512,514],{"id":513},"app-改版要多久","APP 改版要多久？",[113,516,517],{},"先預留盤點與上架一個小版本的時間，之後依改版範圍分版上線。範圍小的改版可以在幾個版本內完成，大改版或整併建議拆成多個階段，每個階段都能獨立上線。",[490,519,521],{"id":520},"改版一定要做-design-system-嗎","改版一定要做 Design System 嗎？",[113,523,524],{},"不一定。只有一支功能單純的 APP，基本的 UI 規範就夠；有多支 APP 或網站要維持一致、或要整併多支 APP 時，才值得建立完整的 Design System。",[490,526,528],{"id":527},"開發者帳號應該用誰的名義申請","開發者帳號應該用誰的名義申請？",[113,530,531],{},"用你們公司的名義。開發者帳號是 APP 所有權的所在，用廠商或個人帳號上架，日後換團隊時就得走移轉流程。",{"title":533,"searchDepth":534,"depth":534,"links":535},"",2,[536,537,538,539,540,541,542],{"id":125,"depth":534,"text":126},{"id":208,"depth":534,"text":209},{"id":266,"depth":534,"text":267},{"id":320,"depth":534,"text":321},{"id":390,"depth":534,"text":391},{"id":469,"depth":534,"text":470},{"id":488,"depth":534,"text":488,"children":543},[544,546,547,548,549,550],{"id":492,"depth":545,"text":493},3,{"id":499,"depth":545,"text":500},{"id":506,"depth":545,"text":507},{"id":513,"depth":545,"text":514},{"id":520,"depth":545,"text":521},{"id":527,"depth":545,"text":528},"技術分享","\u002Fimages\u002Fblog\u002Fapp-revamp-takeover-guide.webp",null,"APP 要改版或換團隊接手，第一步不是重畫畫面，而是盤點：原始碼、App Store 與 Google Play 的開發者帳號、簽署金鑰、後台與伺服器權限、串接的第三方服務。盤點完成、確認新團隊能自己重新打包上架，才開始改功能。改版後由誰維運要先談好；Design System 則看產品數量與改版頻率決定，多平台、持續改版的才值得做完整版本。","md",false,"zh-tw",{},true,"舊系統","\u002Fzh-tw\u002Farticle\u002Fapp-revamp-takeover-guide",{"title":108,"description":554},[564,566,568,570],{"name":310,"issuer":565},"Apple（App Store Connect 說明）",{"name":262,"issuer":567},"Google（Play Console 說明）",{"name":569,"issuer":567},"Transfer apps to a different developer account",{"name":571,"issuer":572},"Meet Google Play's target API level requirement","Google（Android Developers）","zh-tw\u002Farticle\u002Fapp-revamp-takeover-guide",[575,576,577,578,579],"APP 改版或接手的第一步是盤點，不是重畫畫面：原始碼、開發者帳號、簽署金鑰、伺服器權限與第三方服務都要確認拿得到。","新團隊先證明能自己重新打包、上架一個小版本，再開始改功能，上線中的服務才不會中斷。","開發者帳號在客戶名下最好；不在的話，Apple 與 Google 都提供在開發者帳號之間移轉 APP 的流程，評分與下載紀錄可以保留。","改版後誰來維運要在合約裡寫清楚：iOS、Android 每年改版，商店規定也會變，沒人負責的 APP 很快就不能更新。","Design System 不是每支 APP 都要做：多產品、多平台、持續改版才值得做完整版本，單一小 APP 先建立基本的 UI 規範就夠。","2026\u002F11\u002F04","blog","eS1NY2A1ESl_4ZfAuXJDiO1dkv4OfdX_x9j-8PVVPHI",[584,588,593],{"slug":585,"title":586,"time":580,"cover":587,"need":560},"ai-coding-tools-legacy-system-refactoring","用 Claude Code 這類 AI 工具改版既有系統：盤點、測試、逐步替換與審查","\u002Fimages\u002Fblog\u002Fai-coding-tools-legacy-system-refactoring.webp",{"slug":589,"title":590,"time":591,"cover":592,"need":560},"legacy-system-takeover-guide","系統沒人維護怎麼辦？舊系統接手、重構與重寫的完整指南","2026\u002F07\u002F28","\u002Fimages\u002Fblog\u002Flegacy-system-takeover-guide.webp",{"slug":594,"title":595,"time":596,"cover":597,"need":560},"2026-system-maintenance-5-benefits-digital-assets","系統維運能為企業帶來哪些優勢？掌握 5 大好處確保數位資產穩定增值","2026\u002F04\u002F17","\u002Fimages\u002Fblog\u002F2026-system-maintenance-5-benefits-digital-assets.webp",1794558627560]