[{"data":1,"prerenderedAt":2817},["ShallowReactive",2],{"blog-\u002Fblog\u002Fmini-program\u002Fxiaochengxu-gaiban":3,"blog-related-\u002Fblog\u002Fmini-program\u002Fxiaochengxu-gaiban":998},{"id":4,"title":5,"author":6,"body":7,"category":966,"cover":967,"date":968,"description":969,"draft":970,"extension":971,"faq":972,"featured":970,"image":967,"keywords":982,"meta":987,"navigation":988,"path":989,"seo":990,"sitemap":991,"stem":992,"tags":993,"updated":968,"__hash__":997},"blog\u002Fblog\u002Fmini-program\u002Fxiaochengxu-gaiban.md","小程序改版升级怎么做才不出问题","HNREIS",{"type":8,"value":9,"toc":926},"minimark",[10,19,23,28,41,45,56,60,71,75,86,90,98,104,107,194,200,203,207,260,264,309,313,358,362,365,434,440,444,489,493,496,549,555,559,562,615,619,622,675,678,682,693,697,707,711,721,725,735,739,749,753,763,766,769,773,784,788,796,800,808,812,823,826,829,849,852,890,893,920],[11,12,13,14,18],"p",{},"小程序做了几年，UI 老了、功能跟不上了、性能差了，要改版升级。",[15,16,17],"strong",{},"改版不是简单换个 UI——数据要保住、功能不能崩、用户要不流失。"," 这篇讲清怎么改版才不出问题。",[20,21,22],"h2",{"id":22},"为什么要改版",[24,25,27],"h3",{"id":26},"_1-uiux-落后","1. UI\u002FUX 落后",[29,30,31,35,38],"ul",{},[32,33,34],"li",{},"设计风格过时。",[32,36,37],{},"体验不如新竞品。",[32,39,40],{},"不符合品牌升级。",[24,42,44],{"id":43},"_2-功能跟不上","2. 功能跟不上",[29,46,47,50,53],{},[32,48,49],{},"业务扩展，原功能不够。",[32,51,52],{},"营销玩法跟不上。",[32,54,55],{},"用户需求变化。",[24,57,59],{"id":58},"_3-技术债","3. 技术债",[29,61,62,65,68],{},[32,63,64],{},"技术栈老旧（PHP\u002FjQuery）。",[32,66,67],{},"代码混乱、难维护。",[32,69,70],{},"性能问题（卡顿\u002F白屏）。",[24,72,74],{"id":73},"_4-数据问题","4. 数据问题",[29,76,77,80,83],{},[32,78,79],{},"数据结构不合理。",[32,81,82],{},"数据冗余\u002F丢失。",[32,84,85],{},"难以分析。",[24,87,89],{"id":88},"_5-安全问题","5. 安全问题",[29,91,92,95],{},[32,93,94],{},"漏洞多。",[32,96,97],{},"不符合新合规要求。",[11,99,100,103],{},[15,101,102],{},"改版前要评估必要性和成本","，不是\"看着不爽就改\"。",[20,105,106],{"id":106},"改版的几种类型",[108,109,110,126],"table",{},[111,112,113],"thead",{},[114,115,116,120,123],"tr",{},[117,118,119],"th",{},"类型",[117,121,122],{},"说明",[117,124,125],{},"成本",[127,128,129,141,152,162,173,183],"tbody",{},[114,130,131,135,138],{},[132,133,134],"td",{},"UI 改版",[132,136,137],{},"只改界面",[132,139,140],{},"低",[114,142,143,146,149],{},[132,144,145],{},"功能扩展",[132,147,148],{},"加新功能",[132,150,151],{},"中",[114,153,154,157,160],{},[132,155,156],{},"流程优化",[132,158,159],{},"改用户操作流程",[132,161,151],{},[114,163,164,167,170],{},[132,165,166],{},"技术重构",[132,168,169],{},"换技术栈",[132,171,172],{},"高",[114,174,175,178,181],{},[132,176,177],{},"数据重构",[132,179,180],{},"改数据库结构",[132,182,172],{},[114,184,185,188,191],{},[132,186,187],{},"推倒重做",[132,189,190],{},"全部重做",[132,192,193],{},"最高",[11,195,196,199],{},[15,197,198],{},"多数改版是组合","，比如 UI 改版 + 功能扩展。",[20,201,202],{"id":202},"改版的流程",[24,204,206],{"id":205},"_1-现状评估","1. 现状评估",[108,208,209,218],{},[111,210,211],{},[114,212,213,216],{},[117,214,215],{},"评估",[117,217,122],{},[127,219,220,228,236,244,252],{},[114,221,222,225],{},[132,223,224],{},"现有功能",[132,226,227],{},"列清所有功能",[114,229,230,233],{},[132,231,232],{},"现有数据",[132,234,235],{},"数据量和结构",[114,237,238,241],{},[132,239,240],{},"现有用户",[132,242,243],{},"用户数和活跃度",[114,245,246,249],{},[132,247,248],{},"技术栈",[132,250,251],{},"用什么技术",[114,253,254,257],{},[132,255,256],{},"源码质量",[132,258,259],{},"是否可改",[24,261,263],{"id":262},"_2-改版目标","2. 改版目标",[108,265,266,275],{},[111,267,268],{},[114,269,270,273],{},[117,271,272],{},"目标",[117,274,122],{},[127,276,277,285,293,301],{},[114,278,279,282],{},[132,280,281],{},"业务目标",[132,283,284],{},"改版要解决什么业务问题",[114,286,287,290],{},[132,288,289],{},"用户目标",[132,291,292],{},"提升什么用户体验",[114,294,295,298],{},[132,296,297],{},"技术目标",[132,299,300],{},"解决什么技术问题",[114,302,303,306],{},[132,304,305],{},"数据目标",[132,307,308],{},"数据要怎么变",[24,310,312],{"id":311},"_3-设计新方案","3. 设计新方案",[108,314,315,324],{},[111,316,317],{},[114,318,319,322],{},[117,320,321],{},"设计",[117,323,122],{},[127,325,326,334,342,350],{},[114,327,328,331],{},[132,329,330],{},"UI 设计",[132,332,333],{},"新界面",[114,335,336,339],{},[132,337,338],{},"架构设计",[132,340,341],{},"新技术架构",[114,343,344,347],{},[132,345,346],{},"数据设计",[132,348,349],{},"新数据库结构",[114,351,352,355],{},[132,353,354],{},"迁移方案",[132,356,357],{},"数据怎么迁移",[24,359,361],{"id":360},"_4-数据迁移关键","4. 数据迁移（关键）",[11,363,364],{},"数据迁移是改版最大风险：",[108,366,367,376],{},[111,368,369],{},[114,370,371,374],{},[117,372,373],{},"步骤",[117,375,122],{},[127,377,378,386,394,402,410,418,426],{},[114,379,380,383],{},[132,381,382],{},"1. 数据备份",[132,384,385],{},"全量备份现有数据",[114,387,388,391],{},[132,389,390],{},"2. 数据清洗",[132,392,393],{},"清理脏数据",[114,395,396,399],{},[132,397,398],{},"3. 字段映射",[132,400,401],{},"旧字段 → 新字段",[114,403,404,407],{},[132,405,406],{},"4. 试迁移",[132,408,409],{},"测试环境试迁",[114,411,412,415],{},[132,413,414],{},"5. 正式迁移",[132,416,417],{},"正式环境迁移",[114,419,420,423],{},[132,421,422],{},"6. 数据校验",[132,424,425],{},"校验迁移后数据",[114,427,428,431],{},[132,429,430],{},"7. 回滚方案",[132,432,433],{},"出问题能回滚",[11,435,436,439],{},[15,437,438],{},"数据迁移前必须备份","——出问题能恢复。",[24,441,443],{"id":442},"_5-开发","5. 开发",[108,445,446,455],{},[111,447,448],{},[114,449,450,453],{},[117,451,452],{},"工作",[117,454,122],{},[127,456,457,465,473,481],{},[114,458,459,462],{},[132,460,461],{},"前端",[132,463,464],{},"新 UI 实现",[114,466,467,470],{},[132,468,469],{},"后端",[132,471,472],{},"新接口和逻辑",[114,474,475,478],{},[132,476,477],{},"数据库",[132,479,480],{},"新结构",[114,482,483,486],{},[132,484,485],{},"集成",[132,487,488],{},"与现有系统集成",[24,490,492],{"id":491},"_6-回归测试关键","6. 回归测试（关键）",[11,494,495],{},"改版后要保证现有功能正常：",[108,497,498,507],{},[111,499,500],{},[114,501,502,505],{},[117,503,504],{},"测试",[117,506,122],{},[127,508,509,517,525,533,541],{},[114,510,511,514],{},[132,512,513],{},"功能测试",[132,515,516],{},"每个功能测一遍",[114,518,519,522],{},[132,520,521],{},"兼容性测试",[132,523,524],{},"不同手机\u002F系统",[114,526,527,530],{},[132,528,529],{},"性能测试",[132,531,532],{},"速度和稳定性",[114,534,535,538],{},[132,536,537],{},"数据测试",[132,539,540],{},"数据正确性",[114,542,543,546],{},[132,544,545],{},"用户测试",[132,547,548],{},"老用户体验",[11,550,551,554],{},[15,552,553],{},"回归测试要全面","——改 A 坏 B 是改版常见问题。",[24,556,558],{"id":557},"_7-灰度发布关键","7. 灰度发布（关键）",[11,560,561],{},"不要一次性全量上线：",[108,563,564,573],{},[111,565,566],{},[114,567,568,571],{},[117,569,570],{},"灰度策略",[117,572,122],{},[127,574,575,583,591,599,607],{},[114,576,577,580],{},[132,578,579],{},"内部测试",[132,581,582],{},"公司内部先用",[114,584,585,588],{},[132,586,587],{},"小范围灰度",[132,589,590],{},"5%\u002F10%\u002F50% 用户",[114,592,593,596],{},[132,594,595],{},"监控数据",[132,597,598],{},"看是否有问题",[114,600,601,604],{},[132,602,603],{},"全量发布",[132,605,606],{},"没问题后全量",[114,608,609,612],{},[132,610,611],{},"回滚准备",[132,613,614],{},"出问题秒回滚",[24,616,618],{"id":617},"_8-用户引导关键","8. 用户引导（关键）",[11,620,621],{},"老用户可能不适应新版本：",[108,623,624,633],{},[111,625,626],{},[114,627,628,631],{},[117,629,630],{},"引导",[117,632,122],{},[127,634,635,643,651,659,667],{},[114,636,637,640],{},[132,638,639],{},"改版公告",[132,641,642],{},"提前告知用户",[114,644,645,648],{},[132,646,647],{},"新功能介绍",[132,649,650],{},"上线后介绍",[114,652,653,656],{},[132,654,655],{},"引导浮层",[132,657,658],{},"第一次用引导",[114,660,661,664],{},[132,662,663],{},"反馈渠道",[132,665,666],{},"让用户提意见",[114,668,669,672],{},[132,670,671],{},"过渡期",[132,673,674],{},"老版本保留一段时间",[20,676,677],{"id":677},"改版的常见坑",[24,679,681],{"id":680},"_1-数据丢失","1. 数据丢失",[29,683,684,687],{},[32,685,686],{},"改数据库结构时丢历史数据。",[32,688,689,692],{},[15,690,691],{},"解决","：备份 + 校验。",[24,694,696],{"id":695},"_2-功能崩","2. 功能崩",[29,698,699,702],{},[32,700,701],{},"改 A 坏 B。",[32,703,704,706],{},[15,705,691],{},"：回归测试。",[24,708,710],{"id":709},"_3-性能下降","3. 性能下降",[29,712,713,716],{},[32,714,715],{},"新版本更卡。",[32,717,718,720],{},[15,719,691],{},"：性能测试 + 优化。",[24,722,724],{"id":723},"_4-用户不适应","4. 用户不适应",[29,726,727,730],{},[32,728,729],{},"界面大变，老用户找不到功能。",[32,731,732,734],{},[15,733,691],{},"：用户引导 + 过渡期。",[24,736,738],{"id":737},"_5-上线时间紧","5. 上线时间紧",[29,740,741,744],{},[32,742,743],{},"催着上线，测试不充分。",[32,745,746,748],{},[15,747,691],{},"：合理安排时间，不压缩测试。",[24,750,752],{"id":751},"_6-没回滚方案","6. 没回滚方案",[29,754,755,758],{},[32,756,757],{},"上线崩了无法回滚。",[32,759,760,762],{},[15,761,691],{},"：提前准备回滚方案。",[20,764,765],{"id":765},"改版的成本控制",[11,767,768],{},"改版容易超预算，控制方法：",[24,770,772],{"id":771},"_1-分阶段改","1. 分阶段改",[29,774,775,778,781],{},[32,776,777],{},"不要一次改完。",[32,779,780],{},"分阶段（先 UI 后功能后技术）。",[32,782,783],{},"每阶段验证效果。",[24,785,787],{"id":786},"_2-保留可用部分","2. 保留可用部分",[29,789,790,793],{},[32,791,792],{},"能用的代码不要重写。",[32,794,795],{},"只改必须改的。",[24,797,799],{"id":798},"_3-用成熟方案","3. 用成熟方案",[29,801,802,805],{},[32,803,804],{},"不重复造轮子。",[32,806,807],{},"用现成组件和模块。",[24,809,811],{"id":810},"_4-客户配合","4. 客户配合",[29,813,814,817,820],{},[32,815,816],{},"需求明确（不边做边改）。",[32,818,819],{},"及时反馈。",[32,821,822],{},"不催进度。",[20,824,825],{"id":825},"改版合同要点",[11,827,828],{},"改版合同要明确：",[29,830,831,834,837,840,843,846],{},[32,832,833],{},"改动范围（清单）。",[32,835,836],{},"现有功能不破坏的承诺。",[32,838,839],{},"数据安全（不丢数据）。",[32,841,842],{},"验收标准。",[32,844,845],{},"回滚方案。",[32,847,848],{},"维护期。",[20,850,851],{"id":851},"常见误区",[29,853,854,860,866,872,878,884],{},[32,855,856,859],{},[15,857,858],{},"改版就是换 UI","：实际涉及很多。",[32,861,862,865],{},[15,863,864],{},"不评估就改","：改到一半发现做不下去。",[32,867,868,871],{},[15,869,870],{},"不备份就改","：数据丢了无法恢复。",[32,873,874,877],{},[15,875,876],{},"不做回归测试","：改 A 坏 B。",[32,879,880,883],{},[15,881,882],{},"一次性全量上线","：出问题影响所有用户。",[32,885,886,889],{},[15,887,888],{},"不引导用户","：老用户不适应流失。",[20,891,892],{"id":892},"怎么开始",[894,895,896,899,902,905,908,911,914,917],"ol",{},[32,897,898],{},"评估现状（功能\u002F数据\u002F技术）。",[32,900,901],{},"明确改版目标和范围。",[32,903,904],{},"设计新方案。",[32,906,907],{},"制定数据迁移方案（含备份）。",[32,909,910],{},"开发 + 回归测试。",[32,912,913],{},"灰度发布。",[32,915,916],{},"用户引导。",[32,918,919],{},"持续优化。",[921,922,923],"blockquote",{},[11,924,925],{},"广州市汉诺雷斯（HNREIS）做过多个小程序改版项目，会先评估再设计、严格测试和灰度发布，避免改版翻车。把你的改版需求告诉我们，我们给出方案与报价。",{"title":927,"searchDepth":928,"depth":928,"links":929},"",2,[930,938,939,949,957,963,964,965],{"id":22,"depth":928,"text":22,"children":931},[932,934,935,936,937],{"id":26,"depth":933,"text":27},3,{"id":43,"depth":933,"text":44},{"id":58,"depth":933,"text":59},{"id":73,"depth":933,"text":74},{"id":88,"depth":933,"text":89},{"id":106,"depth":928,"text":106},{"id":202,"depth":928,"text":202,"children":940},[941,942,943,944,945,946,947,948],{"id":205,"depth":933,"text":206},{"id":262,"depth":933,"text":263},{"id":311,"depth":933,"text":312},{"id":360,"depth":933,"text":361},{"id":442,"depth":933,"text":443},{"id":491,"depth":933,"text":492},{"id":557,"depth":933,"text":558},{"id":617,"depth":933,"text":618},{"id":677,"depth":928,"text":677,"children":950},[951,952,953,954,955,956],{"id":680,"depth":933,"text":681},{"id":695,"depth":933,"text":696},{"id":709,"depth":933,"text":710},{"id":723,"depth":933,"text":724},{"id":737,"depth":933,"text":738},{"id":751,"depth":933,"text":752},{"id":765,"depth":928,"text":765,"children":958},[959,960,961,962],{"id":771,"depth":933,"text":772},{"id":786,"depth":933,"text":787},{"id":798,"depth":933,"text":799},{"id":810,"depth":933,"text":811},{"id":825,"depth":928,"text":825},{"id":851,"depth":928,"text":851},{"id":892,"depth":928,"text":892},"mini-program",null,"2026-04-19","小程序改版升级最容易出问题——数据丢失、功能崩、用户不适应。本文讲清改版的评估、流程、数据迁移、回归测试、灰度发布，避免改版翻车。",false,"md",[973,976,979],{"q":974,"a":975},"小程序什么时候需要改版？","几种情况：UI 老旧跟不上品牌、功能跟不上业务、技术栈老旧维护难、性能差（卡顿\u002F白屏）、用户反馈差。改版前要评估必要性和成本，不是\"看着不爽就改\"。",{"q":977,"a":978},"小程序改版最大风险是什么？","三个：数据丢失（改数据库结构时丢历史数据）、功能崩（改 A 坏 B）、用户不适应（界面大变老用户找不到）。每个都要有应对方案：备份、回归测试、灰度发布。",{"q":980,"a":981},"小程序改版多少钱？","看改动范围。UI 改版（不改功能）2-4 万；功能扩展改版 4-8 万；技术栈重构 8-15 万；推倒重做 10-20 万。在原代码上改比新做省 30-50%。",[983,984,985,986],"小程序改版","小程序升级","数据迁移","灰度发布",{},true,"\u002Fblog\u002Fmini-program\u002Fxiaochengxu-gaiban",{"title":5,"description":969},{"loc":989},"blog\u002Fmini-program\u002Fxiaochengxu-gaiban",[994,995,996],"改版","升级","重构","dEHlc-kFYQkL0y-kMFFFT_Phpsai4Z3ZuSD6SC9ySHk",[999,1405,1860,2377],{"id":1000,"title":1001,"author":6,"body":1002,"category":966,"cover":967,"date":1380,"description":1381,"draft":970,"extension":971,"faq":1382,"featured":970,"image":967,"keywords":1392,"meta":1397,"navigation":988,"path":1398,"seo":1399,"sitemap":1400,"stem":1401,"tags":1402,"updated":1380,"__hash__":1404},"blog\u002Fblog\u002Fmini-program\u002Fapp-zhuan-xiaochengxu.md","App转小程序怎么做：功能裁剪与迁移",{"type":8,"value":1003,"toc":1362},[1004,1011,1015,1018,1032,1039,1043,1124,1130,1133,1137,1140,1144,1164,1168,1174,1177,1181,1189,1193,1204,1208,1219,1222,1228,1231,1245,1248,1298,1301,1303,1335,1337,1357],[11,1005,1006,1007,1010],{},"很多企业的 App 做完了发现下载量上不去，又想做小程序。",[15,1008,1009],{},"App 转小程序不是把 App 搬过去，而是按小程序场景重新裁剪和设计。"," 这篇讲清怎么迁移才不出问题。",[20,1012,1014],{"id":1013},"为什么要从-app-转到小程序","为什么要从 App 转到小程序",[11,1016,1017],{},"App 和小程序是两种定位：",[29,1019,1020,1026],{},[32,1021,1022,1025],{},[15,1023,1024],{},"App","：功能全、体验重、留存好，但下载门槛高、获客贵。",[32,1027,1028,1031],{},[15,1029,1030],{},"小程序","：即用即走、易传播、获客成本低，但功能受限。",[11,1033,1034,1035,1038],{},"很多企业的现实是：",[15,1036,1037],{},"App 装机量起不来，营销全靠小程序引流。"," 这时把 App 的核心场景做进小程序，是性价比最高的策略。",[20,1040,1042],{"id":1041},"app-转小程序的核心矛盾","App 转小程序的核心矛盾",[108,1044,1045,1056],{},[111,1046,1047],{},[114,1048,1049,1052,1054],{},[117,1050,1051],{},"维度",[117,1053,1024],{},[117,1055,1030],{},[127,1057,1058,1069,1080,1091,1102,1113],{},[114,1059,1060,1063,1066],{},[132,1061,1062],{},"包大小",[132,1064,1065],{},"几十到几百 MB",[132,1067,1068],{},"主包 ≤ 2MB（分包 ≤ 20MB）",[114,1070,1071,1074,1077],{},[132,1072,1073],{},"性能",[132,1075,1076],{},"原生性能",[132,1078,1079],{},"受微信容器限制",[114,1081,1082,1085,1088],{},[132,1083,1084],{},"功能",[132,1086,1087],{},"无限制",[132,1089,1090],{},"受 API 白名单限制",[114,1092,1093,1096,1099],{},[132,1094,1095],{},"推送",[132,1097,1098],{},"自由",[132,1100,1101],{},"订阅消息受限",[114,1103,1104,1107,1110],{},[132,1105,1106],{},"后台运行",[132,1108,1109],{},"支持",[132,1111,1112],{},"不支持（除特定类目）",[114,1114,1115,1118,1121],{},[132,1116,1117],{},"用户入口",[132,1119,1120],{},"应用商店",[132,1122,1123],{},"微信内（搜一搜、扫码、分享）",[11,1125,1126,1129],{},[15,1127,1128],{},"照搬 App 必然踩坑","——包超限、加载慢、功能无法实现。",[20,1131,1132],{"id":1132},"怎么做功能裁剪",[24,1134,1136],{"id":1135},"第-1-步列清-app-的所有功能模块","第 1 步：列清 App 的所有功能模块",[11,1138,1139],{},"把 App 的功能拉一个清单，标注使用频率和价值。",[24,1141,1143],{"id":1142},"第-2-步分三类处理","第 2 步：分三类处理",[29,1145,1146,1152,1158],{},[32,1147,1148,1151],{},[15,1149,1150],{},"核心迁移","：高频、轻量、能在小程序内闭环的功能（如下单、查询、预约、会员）——做进小程序。",[32,1153,1154,1157],{},[15,1155,1156],{},"保留 App","：低频、重交互、依赖原生能力（如视频编辑、复杂图表、传感器）——留在 App。",[32,1159,1160,1163],{},[15,1161,1162],{},"砍掉","：没人用的功能——趁机清理。",[24,1165,1167],{"id":1166},"第-3-步重新设计交互","第 3 步：重新设计交互",[11,1169,1170,1171],{},"App 的多层级导航、复杂手势在小程序里要简化。",[15,1172,1173],{},"小程序的首屏要让用户 3 秒内找到要用的功能。",[20,1175,1176],{"id":1176},"迁移的技术选择",[24,1178,1180],{"id":1179},"方案-a原生小程序wxmlwxssjs","方案 A：原生小程序（WXML\u002FWXSS\u002FJS）",[29,1182,1183,1186],{},[32,1184,1185],{},"性能最好，体验最贴近微信。",[32,1187,1188],{},"缺点：只能跑微信，代码无法复用到其他端。",[24,1190,1192],{"id":1191},"方案-b跨端框架taro-uni-app","方案 B：跨端框架（Taro \u002F uni-app）",[29,1194,1195,1198,1201],{},[32,1196,1197],{},"一套代码编译到微信、支付宝、App、H5 多端。",[32,1199,1200],{},"适合：后续还想做 App 或其他小程序。",[32,1202,1203],{},"代价：性能比原生略差，调试复杂度更高。",[24,1205,1207],{"id":1206},"方案-capp-内嵌-h5","方案 C：App 内嵌 H5",[29,1209,1210,1213,1216],{},[32,1211,1212],{},"App 的部分页面用 WebView 套一层壳做成小程序。",[32,1214,1215],{},"成本最低，但体验差、能力受限。",[32,1217,1218],{},"仅适合临时过渡，不推荐长期。",[20,1220,1221],{"id":1221},"后端能不能复用",[11,1223,1224,1227],{},[15,1225,1226],{},"后端接口和数据库基本可以复用","——这是 App 转小程序最大的省成本点。",[11,1229,1230],{},"需要做的是：",[29,1232,1233,1236,1239,1242],{},[32,1234,1235],{},"接入微信登录（替换 App 的手机号\u002F第三方登录）。",[32,1237,1238],{},"接入微信支付（替换 App 支付）。",[32,1240,1241],{},"接入微信订阅消息（替换 App 推送）。",[32,1243,1244],{},"接入微信客服\u002F分享等生态能力。",[20,1246,1247],{"id":1247},"成本参考",[108,1249,1250,1263],{},[111,1251,1252],{},[114,1253,1254,1257,1260],{},[117,1255,1256],{},"阶段",[117,1258,1259],{},"工作量",[117,1261,1262],{},"参考价格",[127,1264,1265,1276,1287],{},[114,1266,1267,1270,1273],{},[132,1268,1269],{},"仅迁移核心功能（轻量）",[132,1271,1272],{},"3-5 周",[132,1274,1275],{},"2-4 万",[114,1277,1278,1281,1284],{},[132,1279,1280],{},"完整迁移（含会员、支付、订单）",[132,1282,1283],{},"6-10 周",[132,1285,1286],{},"5-9 万",[114,1288,1289,1292,1295],{},[132,1290,1291],{},"跨端重构（Taro\u002Funi-app）",[132,1293,1294],{},"8-14 周",[132,1296,1297],{},"7-12 万",[11,1299,1300],{},"实际成本取决于 App 功能复杂度和后端可复用程度。",[20,1302,851],{"id":851},[29,1304,1305,1311,1317,1323,1329],{},[32,1306,1307,1310],{},[15,1308,1309],{},"照搬 App 功能","：导致包超限、加载慢、体验差。",[32,1312,1313,1316],{},[15,1314,1315],{},"保留 App 全部交互","：小程序不是缩小版 App，要重新设计。",[32,1318,1319,1322],{},[15,1320,1321],{},"忽视微信生态","：不做分享、不做订阅消息、不做搜一搜优化，浪费小程序优势。",[32,1324,1325,1328],{},[15,1326,1327],{},"后端不接微信登录","：用户用 App 账号在小程序登不上，体验割裂。",[32,1330,1331,1334],{},[15,1332,1333],{},"指望一套代码全端","：跨端框架能省事，但不可能\"一套通吃\"，仍要分端调优。",[20,1336,892],{"id":892},[894,1338,1339,1342,1345,1348,1351,1354],{},[32,1340,1341],{},"把 App 的功能拉清单，标注频率和价值。",[32,1343,1344],{},"决定哪些迁、哪些留、哪些砍。",[32,1346,1347],{},"选技术方案（原生 \u002F Taro \u002F uni-app）。",[32,1349,1350],{},"后端接入微信登录、支付、订阅消息。",[32,1352,1353],{},"重新设计小程序的交互和首屏。",[32,1355,1356],{},"分批上线，先做核心功能验证。",[921,1358,1359],{},[11,1360,1361],{},"广州市汉诺雷斯（HNREIS）做过多个 App 转小程序的迁移项目，能帮你做功能裁剪决策并实现核心场景的微信端落地。把你 App 的现状和目标告诉我们，我们给出迁移方案与报价。",{"title":927,"searchDepth":928,"depth":928,"links":1363},[1364,1365,1366,1371,1376,1377,1378,1379],{"id":1013,"depth":928,"text":1014},{"id":1041,"depth":928,"text":1042},{"id":1132,"depth":928,"text":1132,"children":1367},[1368,1369,1370],{"id":1135,"depth":933,"text":1136},{"id":1142,"depth":933,"text":1143},{"id":1166,"depth":933,"text":1167},{"id":1176,"depth":928,"text":1176,"children":1372},[1373,1374,1375],{"id":1179,"depth":933,"text":1180},{"id":1191,"depth":933,"text":1192},{"id":1206,"depth":933,"text":1207},{"id":1221,"depth":928,"text":1221},{"id":1247,"depth":928,"text":1247},{"id":851,"depth":928,"text":851},{"id":892,"depth":928,"text":892},"2024-05-11","已有 App 想再做一个微信小程序，怎么把功能迁移过去？本文讲清 App 转小程序的功能裁剪思路、迁移步骤和成本估算，避免照搬 App 导致小程序臃肿、体验差。",[1383,1386,1389],{"q":1384,"a":1385},"已有 App 还要做小程序吗？","通常建议做。App 下载门槛高、获客成本高，而小程序在微信内打开即用、易传播。很多企业用小程序做拉新和轻量场景，App 做深度功能。两者互补，不是二选一。但不要照搬 App 功能，要按小程序场景裁剪。",{"q":1387,"a":1388},"App 转小程序要全部功能都搬过去吗？","不要。小程序定位是\"轻量、即用\"，照搬 App 会臃肿、加载慢、体验差。应该挑高频核心功能（如下单、查询、预约），低频\u002F重交互的功能（如视频剪辑、复杂编辑）留在 App。",{"q":1390,"a":1391},"App 转小程序要重新写代码吗？","大概率要。小程序运行环境和 App 不同（前端语法、组件、API），代码不能直接复用。能复用的是后端接口、数据库、业务逻辑。前端 UI 部分基本重写。技术选型上可以用 Taro\u002Funi-app 跨端框架。",[1393,1394,1395,1396],"App转小程序","App迁移小程序","小程序开发","功能裁剪",{},"\u002Fblog\u002Fmini-program\u002Fapp-zhuan-xiaochengxu",{"title":1001,"description":1381},{"loc":1398},"blog\u002Fmini-program\u002Fapp-zhuan-xiaochengxu",[1403,1396,994],"App迁移","W8xeVbA98MBXYp29j4iNEGDPEITmu190eAKk_jHRrJ0",{"id":1406,"title":1407,"author":6,"body":1408,"category":966,"cover":967,"date":1834,"description":1835,"draft":970,"extension":971,"faq":1836,"featured":970,"image":967,"keywords":1846,"meta":1851,"navigation":988,"path":1852,"seo":1853,"sitemap":1854,"stem":1855,"tags":1856,"updated":1834,"__hash__":1859},"blog\u002Fblog\u002Fmini-program\u002Fb2b-yewu-xiaochengxu.md","企业服务（B2B）小程序：客户管理、报备、报价一体化",{"type":8,"value":1409,"toc":1824},[1410,1417,1421,1438,1442,1448,1462,1467,1481,1486,1497,1502,1516,1521,1532,1536,1607,1613,1617,1675,1681,1684,1715,1717,1764,1768,1800,1802,1819],[11,1411,1412,1413,1416],{},"B2B 业务（批发、经销、企业服务）常被销售管理困扰——外勤销售乱、客户报备撞单、报价混乱、跟进无记录。",[15,1414,1415],{},"B2B 业务小程序能把这些数字化，提升销售管理。"," 这篇讲清怎么做。",[20,1418,1420],{"id":1419},"b2b-业务的痛点","B2B 业务的痛点",[29,1422,1423,1426,1429,1432,1435],{},[32,1424,1425],{},"销售外勤，客户\u002F跟进靠口头微信。",[32,1427,1428],{},"客户报备撞单（多个销售跟进同一客户）。",[32,1430,1431],{},"报价混乱（各报各的，没标准）。",[32,1433,1434],{},"跟进无记录，销售离职客户流失。",[32,1436,1437],{},"数据不透明，管理靠感觉。",[20,1439,1441],{"id":1440},"b2b-业务小程序的核心功能","B2B 业务小程序的核心功能",[11,1443,1444,1447],{},[15,1445,1446],{},"客户管理","：",[29,1449,1450,1453,1456,1459],{},[32,1451,1452],{},"客户档案（公司、联系人、需求）。",[32,1454,1455],{},"客户报备（防撞单）。",[32,1457,1458],{},"客户分配、跟进记录。",[32,1460,1461],{},"客户分级（意向度）。",[11,1463,1464,1447],{},[15,1465,1466],{},"报价",[29,1468,1469,1472,1475,1478],{},[32,1470,1471],{},"在线生成报价单。",[32,1473,1474],{},"标准产品 + 价格体系。",[32,1476,1477],{},"报价审批。",[32,1479,1480],{},"报价记录留存。",[11,1482,1483,1447],{},[15,1484,1485],{},"订单",[29,1487,1488,1491,1494],{},[32,1489,1490],{},"在线下单。",[32,1492,1493],{},"库存查询。",[32,1495,1496],{},"订单状态、审批。",[11,1498,1499,1447],{},[15,1500,1501],{},"销售管理",[29,1503,1504,1507,1510,1513],{},[32,1505,1506],{},"销售业绩、排行。",[32,1508,1509],{},"跟进统计。",[32,1511,1512],{},"外勤打卡\u002F定位。",[32,1514,1515],{},"数据看板。",[11,1517,1518,1447],{},[15,1519,1520],{},"对接",[29,1522,1523,1526,1529],{},[32,1524,1525],{},"ERP（库存、订单）。",[32,1527,1528],{},"CRM（客户深度管理）。",[32,1530,1531],{},"财务（对账、回款）。",[20,1533,1535],{"id":1534},"b2b-小程序-vs-传统-crm","B2B 小程序 vs 传统 CRM",[108,1537,1538,1550],{},[111,1539,1540],{},[114,1541,1542,1544,1547],{},[117,1543,1051],{},[117,1545,1546],{},"B2B 小程序",[117,1548,1549],{},"传统 CRM",[127,1551,1552,1563,1574,1585,1596],{},[114,1553,1554,1557,1560],{},[132,1555,1556],{},"端",[132,1558,1559],{},"移动（手机）",[132,1561,1562],{},"PC 为主",[114,1564,1565,1568,1571],{},[132,1566,1567],{},"复杂度",[132,1569,1570],{},"轻量",[132,1572,1573],{},"复杂",[114,1575,1576,1579,1582],{},[132,1577,1578],{},"场景",[132,1580,1581],{},"外勤\u002F移动操作",[132,1583,1584],{},"深度管理",[114,1586,1587,1590,1593],{},[132,1588,1589],{},"使用",[132,1591,1592],{},"简单",[132,1594,1595],{},"学习成本高",[114,1597,1598,1601,1604],{},[132,1599,1600],{},"适合",[132,1602,1603],{},"销售一线",[132,1605,1606],{},"管理\u002F分析",[11,1608,1609,1612],{},[15,1610,1611],{},"B2B 小程序是\"轻量移动版 CRM\"，和完整 CRM 配合","。",[20,1614,1616],{"id":1615},"选型saas-vs-定制","选型：SaaS vs 定制",[108,1618,1619,1631],{},[111,1620,1621],{},[114,1622,1623,1625,1628],{},[117,1624,1051],{},[117,1626,1627],{},"SaaS",[117,1629,1630],{},"定制",[127,1632,1633,1643,1654,1665],{},[114,1634,1635,1637,1640],{},[132,1636,125],{},[132,1638,1639],{},"几千～几万\u002F年",[132,1641,1642],{},"2-8 万一次性",[114,1644,1645,1648,1651],{},[132,1646,1647],{},"适配业务",[132,1649,1650],{},"标准",[132,1652,1653],{},"深度定制",[114,1655,1656,1659,1662],{},[132,1657,1658],{},"对接现有系统",[132,1660,1661],{},"难",[132,1663,1664],{},"可深度对接",[114,1666,1667,1669,1672],{},[132,1668,1600],{},[132,1670,1671],{},"标准、起步",[132,1673,1674],{},"业务定制、对接 ERP\u002FCRM",[11,1676,1677,1678,1612],{},"B2B 业务逻辑定制性强（报备\u002F报价\u002F审批\u002F对接），",[15,1679,1680],{},"通常定制",[20,1682,1683],{"id":1683},"开发注意",[29,1685,1686,1692,1698,1703,1709],{},[32,1687,1688,1691],{},[15,1689,1690],{},"报备机制","：防撞单是核心，规则要设计好。",[32,1693,1694,1697],{},[15,1695,1696],{},"报价体系","：标准价格 + 灵活报价 + 审批。",[32,1699,1700,1702],{},[15,1701,1520],{},"：ERP\u002FCRM\u002F财务，数据打通。",[32,1704,1705,1708],{},[15,1706,1707],{},"权限","：销售\u002F经理\u002F管理员分级。",[32,1710,1711,1714],{},[15,1712,1713],{},"移动优先","：销售在外勤用，移动端体验要好。",[20,1716,1247],{"id":1247},[108,1718,1719,1730],{},[111,1720,1721],{},[114,1722,1723,1725,1727],{},[117,1724,119],{},[117,1726,1084],{},[117,1728,1729],{},"价格",[127,1731,1732,1742,1753],{},[114,1733,1734,1737,1740],{},[132,1735,1736],{},"基础（定制）",[132,1738,1739],{},"客户+报备+报价+跟进",[132,1741,1275],{},[114,1743,1744,1747,1750],{},[132,1745,1746],{},"完整（定制）",[132,1748,1749],{},"+ 订单+库存+审批+看板+对接",[132,1751,1752],{},"4-8 万",[114,1754,1755,1758,1761],{},[132,1756,1757],{},"复杂（多角色\u002F多区域）",[132,1759,1760],{},"+ 复杂权限\u002F分区域\u002F深度对接",[132,1762,1763],{},"8 万+",[20,1765,1767],{"id":1766},"b2b-业务小程序的价值","B2B 业务小程序的价值",[29,1769,1770,1776,1782,1788,1794],{},[32,1771,1772,1775],{},[15,1773,1774],{},"防撞单","：报备机制，销售不内耗。",[32,1777,1778,1781],{},[15,1779,1780],{},"报价规范","：标准报价 + 审批，不乱。",[32,1783,1784,1787],{},[15,1785,1786],{},"客户留存","：跟进记录，销售离职客户不丢。",[32,1789,1790,1793],{},[15,1791,1792],{},"数据透明","：业绩、跟进、转化可分析。",[32,1795,1796,1799],{},[15,1797,1798],{},"提效","：移动操作，销售效率高。",[20,1801,892],{"id":892},[894,1803,1804,1807,1810,1813,1816],{},[32,1805,1806],{},"盘点销售痛点（报备？报价？跟进？对接？）。",[32,1808,1809],{},"明确要对接的系统（ERP\u002FCRM）。",[32,1811,1812],{},"选 SaaS 还是定制。",[32,1814,1815],{},"设计业务流程（报备\u002F报价\u002F审批）。",[32,1817,1818],{},"分步实施。",[921,1820,1821],{},[11,1822,1823],{},"广州市汉诺雷斯（HNREIS）提供 B2B 业务小程序定制，含客户报备、报价、订单、对接 ERP\u002FCRM。把你的 B2B 业务痛点告诉我们，我们设计方案。",{"title":927,"searchDepth":928,"depth":928,"links":1825},[1826,1827,1828,1829,1830,1831,1832,1833],{"id":1419,"depth":928,"text":1420},{"id":1440,"depth":928,"text":1441},{"id":1534,"depth":928,"text":1535},{"id":1615,"depth":928,"text":1616},{"id":1683,"depth":928,"text":1683},{"id":1247,"depth":928,"text":1247},{"id":1766,"depth":928,"text":1767},{"id":892,"depth":928,"text":892},"2024-05-25","B2B 业务销售外勤、报价混乱、客户报备撞单。本文讲清 B2B 业务小程序如何解决客户管理、报备、报价一体化。",[1837,1840,1843],{"q":1838,"a":1839},"B2B 业务小程序和普通 CRM 有什么区别？","B2B 小程序是\"轻量、移动、聚焦场景\"的 CRM——销售在手机上用（报备客户、查库存、生成报价、跟进记录），比传统 CRM（PC 端、复杂）更轻、更贴合销售外勤场景。通常和完整 CRM 配合（小程序做轻量操作，CRM 做深度管理）。",{"q":1841,"a":1842},"B2B 业务小程序要多少钱？","看功能。基础（客户报备+报价+跟进）定制 2-4 万；带库存查询、订单、审批、数据看板、对接 ERP\u002FCRM 的完整方案，定制 4-8 万。B2B 业务逻辑定制性强，通常定制。",{"q":1844,"a":1845},"客户报备防撞单怎么做？","客户报备机制：销售先报备客户（客户名+联系人+时间），系统判断是否已被他人报备，已报备的不能重复跟进。报备信息+跟进记录留存，避免撞单和抢单纠纷，也保护销售积极性。",[1847,1848,1849,1850],"B2B业务小程序","销售管理小程序","客户报备","报价小程序",{},"\u002Fblog\u002Fmini-program\u002Fb2b-yewu-xiaochengxu",{"title":1407,"description":1835},{"loc":1852},"blog\u002Fmini-program\u002Fb2b-yewu-xiaochengxu",[1857,1578,1858],"B2B","销售","K0R54Ya-AI0CvnrFH8pu6rnzWlppoJltxQuMReCf40g",{"id":1861,"title":1862,"author":6,"body":1863,"category":966,"cover":967,"date":2350,"description":2351,"draft":970,"extension":971,"faq":2352,"featured":970,"image":967,"keywords":2362,"meta":2367,"navigation":988,"path":2368,"seo":2369,"sitemap":2370,"stem":2371,"tags":2372,"updated":2350,"__hash__":2376},"blog\u002Fblog\u002Fmini-program\u002Fbeian-xiaochengxu.md","做小程序需要哪些备案和资质",{"type":8,"value":1864,"toc":2325},[1865,1872,1875,1878,1898,1900,1903,1953,1958,1961,1969,1973,1976,1987,1990,2004,2007,2017,2020,2023,2027,2035,2039,2047,2051,2059,2063,2071,2075,2083,2087,2095,2100,2103,2106,2120,2123,2193,2196,2262,2267,2269,2301,2303,2320],[11,1866,1867,1868,1871],{},"很多企业做完小程序卡在审核上——主体不对、备案没做、资质缺一份，反复打回。",[15,1869,1870],{},"做小程序要先搞清楚资质和备案，避免临上线才发现没法过审。"," 这篇把常见要求讲清楚。",[20,1873,1874],{"id":1874},"小程序的资质体系",[11,1876,1877],{},"小程序要顺利上线，通常要满足三层资质：",[894,1879,1880,1886,1892],{},[32,1881,1882,1885],{},[15,1883,1884],{},"主体认证","：小程序背后的企业\u002F个体户\u002F个人。",[32,1887,1888,1891],{},[15,1889,1890],{},"ICP 备案","：2023 年 9 月起强制要求。",[32,1893,1894,1897],{},[15,1895,1896],{},"行业资质","：根据所选类目额外要求（如餐饮要食品证）。",[20,1899,1884],{"id":1884},[24,1901,1902],{"id":1902},"三种主体类型",[108,1904,1905,1918],{},[111,1906,1907],{},[114,1908,1909,1912,1915],{},[117,1910,1911],{},"主体类型",[117,1913,1914],{},"能做什么",[117,1916,1917],{},"限制",[127,1919,1920,1931,1942],{},[114,1921,1922,1925,1928],{},[132,1923,1924],{},"企业 \u002F 个体户",[132,1926,1927],{},"几乎所有类目（除金融等需特批）",[132,1929,1930],{},"需营业执照",[114,1932,1933,1936,1939],{},[132,1934,1935],{},"政府 \u002F 事业单位",[132,1937,1938],{},"政务、公共服务",[132,1940,1941],{},"需组织机构代码",[114,1943,1944,1947,1950],{},[132,1945,1946],{},"个人",[132,1948,1949],{},"工具、查询、部分内容类",[132,1951,1952],{},"不能支付、不能做电商\u002F医疗\u002F金融等",[11,1954,1955],{},[15,1956,1957],{},"做商业项目，几乎一律用企业或个体户主体。",[24,1959,1960],{"id":1960},"认证费用",[29,1962,1963,1966],{},[32,1964,1965],{},"企业\u002F政府主体：300 元\u002F年认证费（微信支付认证）。",[32,1967,1968],{},"个人主体：免费，但功能受限。",[20,1970,1972],{"id":1971},"icp-备案2023-年-9-月起强制","ICP 备案（2023 年 9 月起强制）",[24,1974,1975],{"id":1975},"谁要备案",[29,1977,1978,1984],{},[32,1979,1980,1983],{},[15,1981,1982],{},"所有新上线的小程序都要备案","（无论主体类型）。",[32,1985,1986],{},"2023 年 9 月前已上线的小程序也要补备案。",[24,1988,1989],{"id":1989},"备案流程",[894,1991,1992,1995,1998,2001],{},[32,1993,1994],{},"在小程序后台提交备案信息（主体信息、负责人、小程序信息）。",[32,1996,1997],{},"上传材料（营业执照、身份证、域名验证文件等）。",[32,1999,2000],{},"微信初审 → 通信管理局审核。",[32,2002,2003],{},"审核通过下发备案号。",[24,2005,2006],{"id":2006},"备案时间",[11,2008,2009,2010,2013,2014],{},"通常 ",[15,2011,2012],{},"1-3 周","，遇到材料问题会打回重审。",[15,2015,2016],{},"要预留充足时间，别临上线才办。",[20,2018,2019],{"id":2019},"行业资质要求",[11,2021,2022],{},"不同服务类目对应不同资质，常见场景：",[24,2024,2026],{"id":2025},"餐饮-食品","餐饮 \u002F 食品",[29,2028,2029,2032],{},[32,2030,2031],{},"食品经营许可证",[32,2033,2034],{},"餐饮服务许可证（如适用）",[24,2036,2038],{"id":2037},"医疗-健康","医疗 \u002F 健康",[29,2040,2041,2044],{},[32,2042,2043],{},"医疗机构执业许可证",[32,2045,2046],{},"互联网医疗信息服务审核（如做线上问诊）",[24,2048,2050],{"id":2049},"教育-培训","教育 \u002F 培训",[29,2052,2053,2056],{},[32,2054,2055],{},"办学许可证（学科类）",[32,2057,2058],{},"ICP 经营许可证（如做在线课程付费）",[24,2060,2062],{"id":2061},"金融-保险","金融 \u002F 保险",[29,2064,2065,2068],{},[32,2066,2067],{},"金融牌照（银行\u002F证券\u002F保险）",[32,2069,2070],{},"互联网保险业务批复",[24,2072,2074],{"id":2073},"电商-零售","电商 \u002F 零售",[29,2076,2077,2080],{},[32,2078,2079],{},"营业执照（一般即可）",[32,2081,2082],{},"涉及特殊商品（烟草、酒类）需专项资质",[24,2084,2086],{"id":2085},"文化-娱乐","文化 \u002F 娱乐",[29,2088,2089,2092],{},[32,2090,2091],{},"网络文化经营许可证（音视频、直播）",[32,2093,2094],{},"出版物经营许可证（电子书、纸质书销售）",[11,2096,2097],{},[15,2098,2099],{},"具体到每个子类目，微信后台的\"服务类目\"页面会列出对应的资质清单，对照准备即可。",[20,2101,2102],{"id":2102},"微信支付资质",[11,2104,2105],{},"要用微信支付收款，要额外满足：",[29,2107,2108,2111,2114,2117],{},[32,2109,2110],{},"企业或个体户主体（个人不行）。",[32,2112,2113],{},"提供对公账户或法人对私账户。",[32,2115,2116],{},"经营范围覆盖实际业务。",[32,2118,2119],{},"部分高风险行业要满足更高门槛（如虚拟商品、特定类目）。",[20,2121,2122],{"id":2122},"常见踩坑场景",[108,2124,2125,2136],{},[111,2126,2127],{},[114,2128,2129,2131,2134],{},[117,2130,1578],{},[117,2132,2133],{},"问题",[117,2135,691],{},[127,2137,2138,2149,2160,2171,2182],{},[114,2139,2140,2143,2146],{},[132,2141,2142],{},"个人主体想做电商",[132,2144,2145],{},"类目不让选",[132,2147,2148],{},"改用个体户或企业主体",[114,2150,2151,2154,2157],{},[132,2152,2153],{},"涉及医疗咨询",[132,2155,2156],{},"缺医疗机构许可证",[132,2158,2159],{},"选其他类目或办证",[114,2161,2162,2165,2168],{},[132,2163,2164],{},"没做 ICP 备案",[132,2166,2167],{},"无法提交审核",[132,2169,2170],{},"先备案再开发",[114,2172,2173,2176,2179],{},[132,2174,2175],{},"经营范围不匹配",[132,2177,2178],{},"微信支付申请被拒",[132,2180,2181],{},"调整营业执照经营范围",[114,2183,2184,2187,2190],{},[132,2185,2186],{},"直播带货",[132,2188,2189],{},"缺网络文化经营许可证",[132,2191,2192],{},"选短视频\u002F录播形式",[20,2194,2195],{"id":2195},"时间和成本参考",[108,2197,2198,2211],{},[111,2199,2200],{},[114,2201,2202,2205,2208],{},[117,2203,2204],{},"项目",[117,2206,2207],{},"时间",[117,2209,2210],{},"费用",[127,2212,2213,2223,2232,2242,2252],{},[114,2214,2215,2217,2220],{},[132,2216,1884],{},[132,2218,2219],{},"1-3 天",[132,2221,2222],{},"300 元\u002F年",[114,2224,2225,2227,2229],{},[132,2226,1890],{},[132,2228,2012],{},[132,2230,2231],{},"免费",[114,2233,2234,2236,2239],{},[132,2235,2031],{},[132,2237,2238],{},"2-4 周",[132,2240,2241],{},"视当地",[114,2243,2244,2247,2250],{},[132,2245,2246],{},"网络文化经营许可证",[132,2248,2249],{},"1-3 个月",[132,2251,2241],{},[114,2253,2254,2257,2260],{},[132,2255,2256],{},"办学许可证",[132,2258,2259],{},"数月",[132,2261,2241],{},[11,2263,2264],{},[15,2265,2266],{},"资质办理往往比开发周期还长，要尽早启动。",[20,2268,851],{"id":851},[29,2270,2271,2277,2283,2289,2295],{},[32,2272,2273,2276],{},[15,2274,2275],{},"先开发后办资质","：发现资质办不下来，整个项目黄了。",[32,2278,2279,2282],{},[15,2280,2281],{},"个人主体硬上商业类目","：审核必拒。",[32,2284,2285,2288],{},[15,2286,2287],{},"忽视 ICP 备案","：以为以前不用就不用，结果卡上线。",[32,2290,2291,2294],{},[15,2292,2293],{},"类目乱选","：选错类目会被驳回，且影响后续支付\u002F能力开通。",[32,2296,2297,2300],{},[15,2298,2299],{},"跨地区经营没考虑","：医疗、教育等行业有地域限制。",[20,2302,892],{"id":892},[894,2304,2305,2308,2311,2314,2317],{},[32,2306,2307],{},"确定主体（企业\u002F个体户）。",[32,2309,2310],{},"查微信小程序后台\"服务类目\"，列出所需资质。",[32,2312,2313],{},"同步启动 ICP 备案和资质办理。",[32,2315,2316],{},"开发期间完成认证和备案。",[32,2318,2319],{},"上线前确认所有资质齐备。",[921,2321,2322],{},[11,2323,2324],{},"广州市汉诺雷斯（HNREIS）做小程序会帮你梳理资质清单和备案流程，把好审核关，让你少走弯路。把你打算做的业务告诉我们，我们给出资质清单和过审方案。",{"title":927,"searchDepth":928,"depth":928,"links":2326},[2327,2328,2332,2337,2345,2346,2347,2348,2349],{"id":1874,"depth":928,"text":1874},{"id":1884,"depth":928,"text":1884,"children":2329},[2330,2331],{"id":1902,"depth":933,"text":1902},{"id":1960,"depth":933,"text":1960},{"id":1971,"depth":928,"text":1972,"children":2333},[2334,2335,2336],{"id":1975,"depth":933,"text":1975},{"id":1989,"depth":933,"text":1989},{"id":2006,"depth":933,"text":2006},{"id":2019,"depth":928,"text":2019,"children":2338},[2339,2340,2341,2342,2343,2344],{"id":2025,"depth":933,"text":2026},{"id":2037,"depth":933,"text":2038},{"id":2049,"depth":933,"text":2050},{"id":2061,"depth":933,"text":2062},{"id":2073,"depth":933,"text":2074},{"id":2085,"depth":933,"text":2086},{"id":2102,"depth":928,"text":2102},{"id":2122,"depth":928,"text":2122},{"id":2195,"depth":928,"text":2195},{"id":851,"depth":928,"text":851},{"id":892,"depth":928,"text":892},"2024-06-02","上线小程序之前要准备哪些资质和备案？本文讲清微信小程序的主体认证、ICP 备案、特殊行业资质要求、类目规则，帮你少踩审核坑、顺利过审上线。",[2353,2356,2359],{"q":2354,"a":2355},"做小程序一定要备案吗？","是的。微信小程序从 2023 年 9 月起要求所有新上线小程序完成 ICP 备案，未备案无法上架。备案主体通常是小程序主体（企业\u002F个体户\u002F个人），备案流程通过微信平台提交，一般 1-3 周完成。",{"q":2357,"a":2358},"个人能做小程序吗？","能，但限制多。个人主体不能做涉及支付、医疗、金融、电商、社交等类目，只能做工具、查询、内容类（部分内容也受限）。涉及商业变现的业务建议用企业或个体户主体。",{"q":2360,"a":2361},"不同行业需要哪些特殊资质？","常见的：餐饮需食品经营许可证；医疗需医疗机构执业许可证；金融需金融牌照；教育办学需办学许可证；出版\u002F音视频需网络文化经营许可证。具体类目对应的资质在微信小程序后台\"服务类目\"页面有清单。",[2363,2364,2365,2366],"小程序备案","小程序资质","ICP备案","类目审核",{},"\u002Fblog\u002Fmini-program\u002Fbeian-xiaochengxu",{"title":1862,"description":2351},{"loc":2368},"blog\u002Fmini-program\u002Fbeian-xiaochengxu",[2373,2374,2375],"备案","资质","审核","fgxf_6vvEWayiU_xBGP8zFxyzrfy6u4g6x3tNZXmiog",{"id":2378,"title":2379,"author":6,"body":2380,"category":966,"cover":967,"date":2790,"description":2791,"draft":970,"extension":971,"faq":2792,"featured":970,"image":967,"keywords":2802,"meta":2807,"navigation":988,"path":2808,"seo":2809,"sitemap":2810,"stem":2811,"tags":2812,"updated":2790,"__hash__":2816},"blog\u002Fblog\u002Fmini-program\u002Fbeijing-xiaochengxu.md","北京企业做小程序怎么选服务商",{"type":8,"value":2381,"toc":2775},[2382,2389,2392,2395,2415,2420,2424,2502,2508,2511,2515,2525,2529,2544,2548,2555,2569,2573,2578,2589,2592,2596,2603,2606,2609,2641,2646,2649,2709,2714,2716,2748,2750,2770],[11,2383,2384,2385,2388],{},"北京企业想做小程序，找本地服务商还是外地？很多老板纠结：本地沟通方便但价格高、选择少，外地便宜但担心不靠谱。",[15,2386,2387],{},"其实小程序开发是天然支持远程协作的，靠谱与否与地域无关。"," 这篇讲清怎么挑。",[20,2390,2391],{"id":2391},"北京小程序服务商的现状",[11,2393,2394],{},"北京本地确实有不少软件公司，但有几个现实：",[29,2396,2397,2403,2409],{},[32,2398,2399,2402],{},[15,2400,2401],{},"价格偏高","：人力成本高，同等质量报价比外地贵 20-40%。",[32,2404,2405,2408],{},[15,2406,2407],{},"选择范围窄","：限于同城，优质团队可能不在北京。",[32,2410,2411,2414],{},[15,2412,2413],{},"不见得更靠谱","：本地也有不规范的团队，远程也有很规范的。",[11,2416,2417],{},[15,2418,2419],{},"\"找本地\"通常是出于信任感的考虑，但不是质量的保证。",[20,2421,2423],{"id":2422},"本地-vs-外地客观对比","本地 vs 外地：客观对比",[108,2425,2426,2438],{},[111,2427,2428],{},[114,2429,2430,2432,2435],{},[117,2431,1051],{},[117,2433,2434],{},"北京本地",[117,2436,2437],{},"外地规范团队",[127,2439,2440,2451,2461,2472,2482,2491],{},[114,2441,2442,2445,2448],{},[132,2443,2444],{},"沟通",[132,2446,2447],{},"可当面",[132,2449,2450],{},"视频 + 文档",[114,2452,2453,2455,2458],{},[132,2454,1729],{},[132,2456,2457],{},"高 20-40%",[132,2459,2460],{},"性价比高",[114,2462,2463,2466,2469],{},[132,2464,2465],{},"选择",[132,2467,2468],{},"限于同城",[132,2470,2471],{},"全国可选",[114,2473,2474,2477,2480],{},[132,2475,2476],{},"流程",[132,2478,2479],{},"看具体公司",[132,2481,2479],{},[114,2483,2484,2487,2489],{},[132,2485,2486],{},"案例",[132,2488,2479],{},[132,2490,2479],{},[114,2492,2493,2496,2499],{},[132,2494,2495],{},"信任建立",[132,2497,2498],{},"见面快",[132,2500,2501],{},"靠流程和合同",[11,2503,2504,2507],{},[15,2505,2506],{},"核心结论","：远近不是判断标准，流程和案例才是。",[20,2509,2510],{"id":2510},"不分地域的判断标准",[24,2512,2514],{"id":2513},"_1-需求与报价的细致度","1. 需求与报价的细致度",[11,2516,2517,2518,2521,2522],{},"靠谱的服务商会先",[15,2519,2520],{},"理需求、出文档、给明细报价","——每个功能点对应的工时和价格列清楚。",[15,2523,2524],{},"张口就报价、不出文档的，警惕。",[24,2526,2528],{"id":2527},"_2-案例真实性","2. 案例真实性",[29,2530,2531,2538,2541],{},[32,2532,2533,2534,2537],{},"有没有",[15,2535,2536],{},"真实可访问的小程序案例","（你能扫码体验）？",[32,2539,2540],{},"能不能提供客户验证（同行可参考）？",[32,2542,2543],{},"编造的案例经不起扫码和追问。",[24,2545,2547],{"id":2546},"_3-合同规范度","3. 合同规范度",[11,2549,2550,2551,2554],{},"敢不敢写",[15,2552,2553],{},"源码归属、违约条款、分期付款、验收标准","？含糊的不签。具体条款：",[29,2556,2557,2560,2563,2566],{},[32,2558,2559],{},"源码交付给你（不是只在服务器部署）。",[32,2561,2562],{},"分期付款（按里程碑）。",[32,2564,2565],{},"验收标准（功能清单 + 测试报告）。",[32,2567,2568],{},"违约责任（延期\u002F质量问题的处理）。",[24,2570,2572],{"id":2571},"_4-流程透明度","4. 流程透明度",[11,2574,2533,2575,1447],{},[15,2576,2577],{},"进度同步机制",[29,2579,2580,2583,2586],{},[32,2581,2582],{},"每周演示可运行版本。",[32,2584,2585],{},"提供可访问的测试环境。",[32,2587,2588],{},"周报同步进展。",[11,2590,2591],{},"问进度含糊的，要警惕。",[24,2593,2595],{"id":2594},"_5-技术栈","5. 技术栈",[11,2597,2598,2599,2602],{},"用的是",[15,2600,2601],{},"现代技术","（Vue\u002FNuxt、Taro、uni-app）还是老旧 PHP\u002FjQuery？技术栈影响后续可维护性和找人成本。",[20,2604,2605],{"id":2605},"远程协作怎么保证质量",[11,2607,2608],{},"很多北京企业担心\"远程不好控\"，其实规范流程比\"能见面\"更靠谱：",[29,2610,2611,2617,2623,2629,2635],{},[32,2612,2613,2616],{},[15,2614,2615],{},"需求文档化","：口头沟通全部落到文档，避免扯皮。",[32,2618,2619,2622],{},[15,2620,2621],{},"每周演示","：可运行版本，你能看到实际进度。",[32,2624,2625,2628],{},[15,2626,2627],{},"视频会议","：关键节点（需求确认、设计评审、验收）视频确认。",[32,2630,2631,2634],{},[15,2632,2633],{},"里程碑验收","：分期付款挂钩交付，验收通过才付下一笔。",[32,2636,2637,2640],{},[15,2638,2639],{},"规范合同","：源码归属、违约、质保白纸黑字。",[11,2642,2643],{},[15,2644,2645],{},"做到这些，远程协作效率和本地没区别。",[20,2647,2648],{"id":2648},"北京小程序开发成本参考",[108,2650,2651,2663],{},[111,2652,2653],{},[114,2654,2655,2657,2660],{},[117,2656,119],{},[117,2658,2659],{},"价格区间",[117,2661,2662],{},"周期",[127,2664,2665,2676,2687,2698],{},[114,2666,2667,2670,2673],{},[132,2668,2669],{},"展示型（企业介绍、产品展示）",[132,2671,2672],{},"1-2 万",[132,2674,2675],{},"2-3 周",[114,2677,2678,2681,2684],{},[132,2679,2680],{},"功能型（电商、预约、会员）",[132,2682,2683],{},"3-6 万",[132,2685,2686],{},"4-8 周",[114,2688,2689,2692,2695],{},[132,2690,2691],{},"业务系统（多角色、订单管理）",[132,2693,2694],{},"6-15 万",[132,2696,2697],{},"8-16 周",[114,2699,2700,2703,2706],{},[132,2701,2702],{},"平台型（多商户、连锁）",[132,2704,2705],{},"10-30 万",[132,2707,2708],{},"12-24 周",[11,2710,2711],{},[15,2712,2713],{},"北京本地服务商通常在区间上限，外地规范团队在区间中下。",[20,2715,851],{"id":851},[29,2717,2718,2724,2730,2736,2742],{},[32,2719,2720,2723],{},[15,2721,2722],{},"\"本地一定靠谱\"","：不规范的本地团队也坑人。",[32,2725,2726,2729],{},[15,2727,2728],{},"\"远程不可控\"","：规范流程下远程完全可行。",[32,2731,2732,2735],{},[15,2733,2734],{},"\"只看价格\"","：低价往往意味着省环节、加价、绑架。",[32,2737,2738,2741],{},[15,2739,2740],{},"\"案例越多越好\"","：案例数量不代表质量，关键看真实性和匹配度。",[32,2743,2744,2747],{},[15,2745,2746],{},"\"合同不重要\"","：合同是出问题时的唯一保障。",[20,2749,892],{"id":892},[894,2751,2752,2755,2758,2761,2764,2767],{},[32,2753,2754],{},"整理你的需求（要做什么功能、给谁用）。",[32,2756,2757],{},"联系 2-3 家服务商（不限地域）。",[32,2759,2760],{},"看是否出需求文档和明细报价。",[32,2762,2763],{},"验证案例真实性。",[32,2765,2766],{},"对比合同条款。",[32,2768,2769],{},"选最匹配的（不是最便宜\u002F最近的）。",[921,2771,2772],{},[11,2773,2774],{},"广州市汉诺雷斯（HNREIS）支持全国远程协作，规范流程保证交付质量不输本地。把你的小程序需求告诉我们，我们出方案和明细报价，北京企业也能高效合作。",{"title":927,"searchDepth":928,"depth":928,"links":2776},[2777,2778,2779,2786,2787,2788,2789],{"id":2391,"depth":928,"text":2391},{"id":2422,"depth":928,"text":2423},{"id":2510,"depth":928,"text":2510,"children":2780},[2781,2782,2783,2784,2785],{"id":2513,"depth":933,"text":2514},{"id":2527,"depth":933,"text":2528},{"id":2546,"depth":933,"text":2547},{"id":2571,"depth":933,"text":2572},{"id":2594,"depth":933,"text":2595},{"id":2605,"depth":928,"text":2605},{"id":2648,"depth":928,"text":2648},{"id":851,"depth":928,"text":851},{"id":892,"depth":928,"text":892},"2024-06-14","北京企业找小程序开发服务商，本地还是外地？本文从案例、合同、流程、性价比几个维度，讲清怎么不分地域挑到靠谱的小程序外包团队。",[2793,2796,2799],{"q":2794,"a":2795},"北京企业一定要找北京本地的小程序公司吗？","不一定。软件开发天然支持远程协作，需求文档化、每周演示、规范合同就能保证交付质量。本地公司的好处是能见面沟通，但选择范围窄、价格偏高。外地规范团队性价比更高，全国都可考虑。",{"q":2797,"a":2798},"怎么判断一家小程序公司靠不靠谱？","看三点：是否先出需求文档和明细报价（不是张口报价）；合同里敢不敢写源码归属、违约条款、分期付款；案例能不能验证（能否演示、能否联系到客户）。三点都含糊的基本不靠谱。",{"q":2800,"a":2801},"北京做小程序大概多少钱？","简单展示型 1-2 万，功能型 3-6 万，复杂业务系统 6-15 万，连锁\u002F多商户平台型 10-30 万。北京本地服务商报价通常比外地高 20-40%，因为人力成本高。",[2803,2804,2805,2806],"北京小程序开发","小程序服务商","小程序外包","软件公司选择",{},"\u002Fblog\u002Fmini-program\u002Fbeijing-xiaochengxu",{"title":2379,"description":2791},{"loc":2808},"blog\u002Fmini-program\u002Fbeijing-xiaochengxu",[2813,2814,2815],"选服务商","北京","远程协作","-homqmHQ5YqnmS4voEUgNcFyYeR1JL6S1bkwQlPnR-E",1781688920074]