[{"data":1,"prerenderedAt":522},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-device-app-development-guide":106,"article-related-zh-tw-device-app-development-guide":505},{"@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":470,"cover":471,"dateModified":472,"description":473,"extension":474,"faq":472,"hasCoverTitle":475,"locale":476,"meta":477,"navigation":478,"need":479,"path":480,"seo":481,"seoDescription":472,"seoTitle":472,"sources":482,"stem":495,"takeaways":496,"time":502,"type":503,"__hash__":504},"content\u002Fzh-tw\u002Farticle\u002Fdevice-app-development-guide.md","設備 APP 開發：硬體廠外包前要準備的 6 件事（藍牙、Wi-Fi、韌體與上架）",{"type":110,"value":111,"toc":445},"minimark",[112,120,125,128,217,221,224,227,230,234,237,240,244,247,250,255,261,264,268,271,274,278,281,284,288,293,297,302,305,310,314,317,394,407,410,414,417,421,424,428,431,435,438,442],[113,114,115,119],"p",{},[116,117,118],"strong",{},"硬體廠要做設備 APP，外包前最該準備的不是畫面設計，而是裝置怎麼和 APP 溝通。"," APP 要透過藍牙或 Wi-Fi 和裝置配對、下指令、讀狀態，所以必須和韌體團隊一起定義指令格式與錯誤處理。以下 6 件事準備好，報價才能比較，開發也比較不會在實機測試時才發現對不上。",[121,122,124],"h2",{"id":123},"外包設備-app-前要先準備哪-6-件事","外包設備 APP 前，要先準備哪 6 件事？",[113,126,127],{},"要準備連線方式、通訊協定文件、雲端後台需求、OTA 更新規劃、多品牌版本需求，以及上架後的維運分工。這 6 件事決定 APP、韌體與雲端各要做多少，也決定費用落在哪個區間。",[129,130,131,147],"table",{},[132,133,134],"thead",{},[135,136,137,141,144],"tr",{},[138,139,140],"th",{},"要準備的事",[138,142,143],{},"要回答的問題",[138,145,146],{},"沒準備好會怎樣",[148,149,150,162,173,184,195,206],"tbody",{},[135,151,152,156,159],{},[153,154,155],"td",{},"連線方式",[153,157,158],{},"藍牙直連、Wi-Fi／雲端，還是閘道器？",[153,160,161],{},"做到一半才發現要離家控制，架構要重來",[135,163,164,167,170],{},[153,165,166],{},"通訊協定文件",[153,168,169],{},"指令格式、回應格式、錯誤碼是什麼？",[153,171,172],{},"實機測試時 APP 和裝置對不上，來回修改",[135,174,175,178,181],{},[153,176,177],{},"雲端後台",[153,179,180],{},"要不要遠端控制、綁帳號、管理多台？",[153,182,183],{},"上市後才補後台，資料與帳號難整合",[135,185,186,189,192],{},[153,187,188],{},"OTA 韌體更新",[153,190,191],{},"韌體出問題時怎麼更新？",[153,193,194],{},"裝置賣出去後無法修正，只能召回或到府處理",[135,196,197,200,203],{},[153,198,199],{},"多品牌版本",[153,201,202],{},"會不會有合作品牌或 OEM 版本？",[153,204,205],{},"每個品牌重寫一次，維護成本加倍",[135,207,208,211,214],{},[153,209,210],{},"上架與維運",[153,212,213],{},"上架帳號是誰的？上架後誰負責改版？",[153,215,216],{},"iOS、Android 改版後藍牙或推播失效，沒人處理",[121,218,220],{"id":219},"藍牙wi-fi-還是閘道器連線方式怎麼選","藍牙、Wi-Fi 還是閘道器，連線方式怎麼選？",[113,222,223],{},"由裝置的硬體與使用情境決定。穿戴裝置、量測儀這類近距離操作的裝置適合藍牙直連；要離家也能控制的家電與換氣設備，需要 Wi-Fi 與雲端；場域內有大量感測器時，才考慮閘道器。",[113,225,226],{},"很多產品會混用，例如先用藍牙配網，再走 Wi-Fi 上雲端。藍牙低功耗（BLE）的連線與資料交換方式，定義在 Bluetooth SIG 的 Bluetooth Core Specification；APP 端要處理的，主要是配對流程、斷線重連，以及不同品牌手機的相容性。",[113,228,229],{},"裝置本身若使用藍牙或 Wi-Fi 等無線射頻，在台灣上市前也要符合國家通訊傳播委員會（NCC）的低功率射頻器材技術規範，這部分由硬體團隊負責，但時程要和 APP 一起排。",[121,231,233],{"id":232},"通訊協定文件要寫到什麼程度","通訊協定文件要寫到什麼程度？",[113,235,236],{},"至少要寫清楚每個指令的格式、裝置的回應格式，以及每種錯誤碼代表什麼。APP 端是照這份文件實作，文件越完整，實機測試時來回修改的次數越少。",[113,238,239],{},"如果韌體還在開發中，可以先約定一份草稿，雙方同時開發，再用實機一起驗證。JoinX 的做法是在需求盤點階段就和韌體團隊對齊通訊協定，再開始設計畫面。",[121,241,243],{"id":242},"什麼時候需要雲端後台與-ota-更新","什麼時候需要雲端後台與 OTA 更新？",[113,245,246],{},"裝置要離家控制、要綁定帳號、要一個人管理多台，或要讓客服查得到裝置狀態時，就需要雲端後台。只要韌體上市後還可能修正或加功能，就要規劃 OTA 更新。",[113,248,249],{},"OTA 更新可以透過 APP 或雲端推送，要能分批更新、失敗可以重試，並在後台看到每台裝置的韌體版本。這些功能如果上市後才補，裝置端的韌體也要跟著改，成本會比一開始就規劃高。",[251,252,254],"h3",{"id":253},"空調換氣設備商淨流換氣系統-app-與管理後台","空調換氣設備商：淨流換氣系統 APP 與管理後台",[113,256,257,260],{},[116,258,259],{},"做法："," 2025 年起為空調換氣設備商開發淨流換氣系統的 APP，接著擴充管理後台與 API，並另外做合作品牌版本的 APP 與年度維護。這個案例從單一裝置 APP 開始，再依產品需要補上後台與品牌版本。",[262,263],"article-cta",{},[121,265,267],{"id":266},"有合作品牌或-oem-版本時app-要怎麼規劃","有合作品牌或 OEM 版本時，APP 要怎麼規劃？",[113,269,270],{},"用同一套程式，依品牌換外觀、名稱與功能組合，分別上架，後台各自管理。這樣不必每個品牌重寫一次，修正一個問題時所有品牌都能一起更新。",[113,272,273],{},"前提是一開始就把「品牌」當成系統的設定，而不是複製一份程式碼。上面的空調換氣設備案例，就是在原本的 APP 與後台上，另外做出合作品牌的版本。",[121,275,277],{"id":276},"上架之後設備-app-還要維護什麼","上架之後，設備 APP 還要維護什麼？",[113,279,280],{},"要維護的主要是作業系統改版。iOS 與 Android 每年改版，藍牙權限、背景執行與推播規則都可能改變；Google Play 也規定 APP 要在期限內支援新的 API 等級，Apple 的審查指南則會更新隱私與權限要求。",[113,282,283],{},"所以設備 APP 上架後，需要有人定期在新版本的手機上檢查配對、控制與推播，並處理送審。上架帳號最好用硬體廠自己的公司帳號，日後更換維護廠商時才不會卡住。",[251,285,287],{"id":286},"咖啡機業者咖啡機操作-app","咖啡機業者：咖啡機操作 APP",[113,289,290,292],{},[116,291,259],{}," 2026 年起開發用手機 APP 操作咖啡機設備的 APP，上線後持續擴充功能。",[251,294,296],{"id":295},"電子儀器公司測量儀-android-app-與-web-版","電子儀器公司：測量儀 Android APP 與 Web 版",[113,298,299,301],{},[116,300,259],{}," 2024 年起開發測量儀的 Android APP，之後追加 Web 版功能，並優化 UI\u002FUX。量測儀器這類近距離操作的裝置，常從單一平台的 APP 開始，再依使用者需要擴充。",[251,303,304],{"id":304},"醫療科技公司與電動車業者",[113,306,307,309],{},[116,308,259],{}," 2025 年為醫療科技公司串接 Apple Watch 健康數據，並蒐集 TrueDepth 深度影像資料；2020 年為電動車業者開發電動車 APP。依保密約定，這些案例以產業描述呈現。",[121,311,313],{"id":312},"設備-app-開發要多少錢要多久","設備 APP 開發要多少錢、要多久？",[113,315,316],{},"依 JoinX 整理的台灣客製專案行情，單一裝置控制 APP 約 NT$50 萬至 120 萬，含帳號、多裝置、雲端後台、推播與 OTA 的功能型約 NT$120 萬至 300 萬，多品牌、大量裝置的平台型從 NT$300 萬起。",[129,318,319,336],{},[132,320,321],{},[135,322,323,326,330,333],{},[138,324,325],{},"範圍",[138,327,329],{"align":328},"right","費用區間",[138,331,332],{},"常見內容",[138,334,335],{},"時程",[148,337,338,352,366,380],{},[135,339,340,343,346,349],{},[153,341,342],{},"需求與通訊協定盤點",[153,344,345],{"align":328},"NT$10 萬～30 萬",[153,347,348],{},"盤點裝置、通訊協定與資料流，產出可比較的規格",[153,350,351],{},"2～4 週",[135,353,354,357,360,363],{},[153,355,356],{},"單一裝置控制 APP",[153,358,359],{"align":328},"NT$50 萬～120 萬",[153,361,362],{},"配對、控制、狀態顯示，含簡易後台",[153,364,365],{},"6～12 週",[135,367,368,371,374,377],{},[153,369,370],{},"功能型",[153,372,373],{"align":328},"NT$120 萬～300 萬",[153,375,376],{},"帳號與多裝置、雲端後台、推播、OTA",[153,378,379],{},"3～6 個月",[135,381,382,385,388,391],{},[153,383,384],{},"平台型",[153,386,387],{"align":328},"NT$300 萬以上",[153,389,390],{},"多品牌版本、大量裝置、資料分析或 AI",[153,392,393],{},"6 個月以上",[113,395,396,397,401,402,406],{},"裝置韌體由硬體團隊負責或另行估價；雲端主機、推播與上架帳號年費依實際用量另計。完整的開發範圍可參考 ",[398,399,24],"a",{"href":400},"\u002Fiot-app\u002F","；藍牙與 Wi-Fi 能帶來哪些商業價值，可參考",[398,403,405],{"href":404},"\u002Farticle\u002Fbluetooth-wifi-iot-business-value\u002F","藍牙、Wi-Fi 與 IoT 如何串聯設備","。",[121,408,409],{"id":409},"常見問題",[251,411,413],{"id":412},"韌體還沒做完可以先開發-app-嗎","韌體還沒做完，可以先開發 APP 嗎？",[113,415,416],{},"可以。先約定一份通訊協定草稿，APP 與韌體同時開發，APP 端可以先用模擬資料做畫面與流程，等韌體可以實機測試時再一起驗證。",[251,418,420],{"id":419},"設備-app-一定要做雲端後台嗎","設備 APP 一定要做雲端後台嗎？",[113,422,423],{},"不一定。只在近距離操作、資料存在手機就夠用的藍牙裝置，可以先不做雲端。要遠端控制、綁帳號、管理多台，或要讓客服查裝置狀態時，才需要雲端後台。",[251,425,427],{"id":426},"上架帳號要用誰的","上架帳號要用誰的？",[113,429,430],{},"建議用硬體廠自己的公司帳號。APP 屬於品牌的資產，用自己的帳號上架，日後更換維護廠商或轉移權限時才不會卡住。",[251,432,434],{"id":433},"一套-app-可以給不同品牌使用嗎","一套 APP 可以給不同品牌使用嗎？",[113,436,437],{},"可以。用同一套程式依品牌換外觀、名稱與功能組合，分別上架，後台各自管理。前提是一開始就把品牌當成系統設定來規劃。",[251,439,441],{"id":440},"設備-app-上架後多久要更新一次","設備 APP 上架後多久要更新一次？",[113,443,444],{},"至少每年要配合 iOS 與 Android 的大改版檢查一次；藍牙權限、背景執行與推播規則改變時，也要即時調整。實際頻率依裝置功能與使用者回報而定。",{"title":446,"searchDepth":447,"depth":447,"links":448},"",2,[449,450,451,452,456,457,462,463],{"id":123,"depth":447,"text":124},{"id":219,"depth":447,"text":220},{"id":232,"depth":447,"text":233},{"id":242,"depth":447,"text":243,"children":453},[454],{"id":253,"depth":455,"text":254},3,{"id":266,"depth":447,"text":267},{"id":276,"depth":447,"text":277,"children":458},[459,460,461],{"id":286,"depth":455,"text":287},{"id":295,"depth":455,"text":296},{"id":304,"depth":455,"text":304},{"id":312,"depth":447,"text":313},{"id":409,"depth":447,"text":409,"children":464},[465,466,467,468,469],{"id":412,"depth":455,"text":413},{"id":419,"depth":455,"text":420},{"id":426,"depth":455,"text":427},{"id":433,"depth":455,"text":434},{"id":440,"depth":455,"text":441},"技術分享","\u002Fimages\u002Fblog\u002Fdevice-app-development-guide.webp",null,"硬體廠要做設備 APP，最常卡住的不是畫面，而是 APP、韌體與雲端對同一個指令的理解不一致。外包前先準備好 6 件事：連線方式、通訊協定文件、要不要雲端後台、OTA 韌體更新、多品牌版本，以及上架後由誰維運。本文用 JoinX 實際做過的換氣設備、咖啡機、量測儀等設備 APP 案例說明每一項怎麼準備，並附上費用區間。","md",false,"zh-tw",{},true,"IoT APP","\u002Fzh-tw\u002Farticle\u002Fdevice-app-development-guide",{"title":108,"description":473},[483,486,489,492],{"name":484,"issuer":485},"Bluetooth Core Specification","Bluetooth SIG",{"name":487,"issuer":488},"低功率射頻器材技術規範","國家通訊傳播委員會（NCC）",{"name":490,"issuer":491},"App Store Review Guidelines","Apple",{"name":493,"issuer":494},"Target API level requirements for Google Play apps","Google","zh-tw\u002Farticle\u002Fdevice-app-development-guide",[497,498,499,500,501],"設備 APP 的難處不在畫面，而在 APP、韌體與雲端對同一個指令的理解要一致，所以通訊協定文件要先準備好。","連線方式由裝置的硬體與使用情境決定：近距離操作用藍牙，要離家控制就需要 Wi-Fi 與雲端。","裝置要遠端控制、綁帳號或管理多台時，就需要雲端後台；韌體要能修正，就要規劃 OTA 更新。","同一套 APP 換品牌上架，比每個品牌重寫一次省成本，但後台要一開始就能分品牌管理。","依 JoinX 的台灣客製專案行情，單一裝置控制 APP 約 NT$50 萬至 120 萬，含雲端與 OTA 的功能型約 NT$120 萬至 300 萬。","2026\u002F11\u002F03","blog","oZ-jMUleB2tinClxok8h4JQZ3D2mJB1P5e_K5rJ5fkY",[506,511,516],{"slug":507,"title":508,"time":509,"cover":510,"need":479},"iot-system-integration-four-layers","IoT 系統整合怎麼選？裝置、閘道、雲端、APP 四層的分工、驗收與費用","2026\u002F11\u002F04","\u002Fimages\u002Fblog\u002Fiot-system-integration-four-layers.webp",{"slug":512,"title":513,"time":514,"cover":515,"need":479},"bluetooth-wifi-iot-business-value","藍牙、Wi-Fi 與 IoT 如何串聯設備、創造商業價值","2025\u002F09\u002F26","\u002Fimages\u002Fblog\u002Fbluetooth-wifi-iot-business-value.webp",{"slug":517,"title":518,"time":519,"cover":520,"need":521},"pos-system-guide","POS 系統怎麼選？套裝、雲端 POS 與客製 POS 的差異、硬體、串接與費用（2026）","2026\u002F11\u002F12","\u002Fimages\u002Fblog\u002Fpos-system-guide.webp","POS 系統",1794558636199]