[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-mobile-context-first-zh-CN":3,"blog-adjacent-mobile-context-first-zh-CN":29,"blog-related-mobile-context-first-zh-CN":65},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":28},65,"mobile-context-first","移动端场景决定交互","把后台功能搬到手机上，第一件事不是缩小屏幕，而是想清楚用户在什么场景下打开它。","\u003Cp>很多客户提出要做移动端，需求文档通常是“把 PC 上的功能都搬过来”。真做出来之后，使用率极低，因为用户在电梯里、车间里、客户现场打开手机，能做的事和坐在电脑前完全不同。\u003C\u002Fp>\n\u003Ch2>先问场景\u003C\u002Fh2>\n\u003Cp>用户在移动端最常做的三件事是什么？通常是查看状态、审批简单事项、拍照上传。\u003C\u002Fp>\n\u003Cp>哪些操作在移动端反而危险？批量删除、复杂配置、金额修改，应该限制或二次确认。\u003C\u002Fp>\n\u003Cp>网络环境如何？车间和仓库可能信号很差，需要离线暂存和自动重试。\u003C\u002Fp>\n\u003Ch2>设计上的取舍\u003C\u002Fh2>\n\u003Cp>首屏只保留高频操作，其余收进二级页面，不要用抽屉把 PC 菜单整个塞进来。\u003C\u002Fp>\n\u003Cp>列表项放足够信息，让用户不点进去就能判断是否需要处理。\u003C\u002Fp>\n\u003Cp>表单尽量少字段，能扫码就不要手输，能用默认值就不要让用户选。\u003C\u002Fp>\n\u003Cp>移动端不是缩小版的后台，而是面向具体场景的另一个产品。想清楚场景，功能自然知道该留哪些。\u003C\u002Fp>","","blue","佳益方圆团队","2026-04-18T16:15:00+08:00",1,false,[16,17,18],"移动端","场景","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","article",50,{},{"previous":30,"next":47},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},45,"observability-for-small-teams","可观测性：日志、指标与追踪","系统出问题时，能回答“发生了什么”比“系统很慢”更有价值。","teal","2026-04-20T16:15:00+08:00",[38,39,40],"可观测性","日志","运维",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":10,"kind":26,"sortOrder":46,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},85,"regression-escape","测试不足复盘：回归漏测的一次事故","一个看似无关的改动，让三个月前修好的问题重新出现。","cyan","2026-04-16T16:15:00+08:00",[55,56,57],"复盘","测试","质量",{"id":59,"parentId":21,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":10,"kind":26,"sortOrder":64,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[66,77,86],{"id":27,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":76},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[73,74,75],"需求","产品方法","风险管理",{"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":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":20,"featured":14,"tags":83,"category":85},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[84,18],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":87,"slug":88,"title":89,"excerpt":90,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":94},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[93,74,73],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21}]