[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-miniapp-or-app-zh-CN":3,"blog-adjacent-miniapp-or-app-zh-CN":29,"blog-related-miniapp-or-app-zh-CN":60},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":13,"readingMinutes":14,"featured":15,"tags":16,"category":19,"seoSettings":28},3,"miniapp-or-app","小程序还是 App？先看业务发生在什么场景","技术偏好不该成为选型依据。低频与高频、分享与留存、能力边界，才是决定载体的关键。","\u003Cp>几乎每个移动端项目都会经历一次“小程序还是 App”的讨论。技术团队各有偏好，业务方则关心预算与上线时间。但真正应该先回答的，是业务发生在什么场景。\u003C\u002Fp>\n\u003Ch2>三类典型场景\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>低频、强分享：\u003C\u002Fstrong>活动报名、品牌展示、预约服务，小程序更合适，用户无需下载，传播路径更短；\u003C\u002Fli>\n\u003Cli>\u003Cstrong>高频、强留存：\u003C\u002Fstrong>会员经营、内部办公、现场作业，App 能提供更稳定的消息、离线与系统能力；\u003C\u002Fli>\n\u003Cli>\u003Cstrong>两者都要：\u003C\u002Fstrong>先用小程序验证需求，再把高频用户沉淀到 App，是更稳妥的节奏。\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>被忽略的成本\u003C\u002Fh2>\n\u003Cp>App 的成本不只在开发：应用商店审核、双端适配、版本兼容、推送通道维护，都是持续投入。小程序也不是“做完就完事”，平台规则、审核要求与包体限制同样需要长期跟进。选型时把这些成本算进去，结论往往更接近现实。\u003C\u002Fp>\n\u003Ch2>我们的建议\u003C\u002Fh2>\n\u003Cp>如果需求还没有被验证，先做小程序；如果业务已经明确依赖高频使用与系统能力，直接做 App；如果不确定，就把两者当作一个连续路径，而不是一次非此即彼的选择。架构上尽量共享业务接口与数据模型，让后续迁移不至于推倒重来。\u003C\u002Fp>\n\u003Cblockquote>真正的成本，不是选错一次技术，而是在错误的选择上反复打补丁。\u003C\u002Fblockquote>\n\u003Cp>工具会变化，用户场景不会。先看清场景，再决定载体。\u003C\u002Fp>","","blue","佳益方圆团队","2026-09-25T09:00:00+08:00","2026-10-18T15:58:14.677+08:00",2,false,[17,18],"移动端","技术选型",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},1,0,"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu","article",60,{},{"previous":30,"next":48},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":20,"featured":15,"tags":37,"category":41},11,"three-lessons-from-first-client","第一单客户教会我们的三件事","2019 年的第一个项目只有三万元，却让我们明白了合同、验收和沟通的分量。","cyan","2026-09-25T10:13:00+08:00",[38,39,40],"创业","客户","合同",{"id":42,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":10,"kind":26,"sortOrder":47,"count":21},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":53,"author":11,"publishedAt":54,"updatedAt":54,"readingMinutes":20,"featured":15,"tags":55,"category":59},32,"rbac-to-data-permissions","权限模型：从角色控制到数据权限","多数后台的权限停在菜单和按钮层面，真正难的是让不同的人只看到自己该看的数据。","indigo","2026-09-23T11:26:00+08:00",[56,57,58],"权限","后台系统","架构",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},[61,72,83],{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":66,"updatedAt":66,"readingMinutes":20,"featured":15,"tags":67,"category":71},30,"integration-api-pitfalls","企业系统集成：接口对接最容易踩的五个坑","接口文档写得再全，真正对接时仍然会卡在字段约定、超时和重复推送这些细节上。","2026-10-17T09:00:00+08:00",[68,69,70],"系统集成","接口","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":20,"slug":73,"title":74,"excerpt":75,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":76,"updatedAt":77,"readingMinutes":14,"featured":78,"tags":79,"category":82},"why-enterprise-systems-age","为什么企业系统会在三年后开始“老化”","系统上线时功能齐全，三年后却处处别扭。问题往往不在代码，而在交付时被忽略的那些变化。","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",true,[80,81],"系统演进","架构设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":84,"slug":85,"title":86,"excerpt":87,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":88,"updatedAt":88,"readingMinutes":20,"featured":15,"tags":89,"category":93},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[90,91,92],"接口设计","幂等","可靠性",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21}]