[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-mobile-context-first-en":3,"blog-adjacent-mobile-context-first-en":29,"blog-related-mobile-context-first-en":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","Mobile Context Decides the Interaction","Moving admin features onto phones does not start with shrinking the screen, but with understanding where users open it.","\u003Cp>Clients often describe mobile work as porting every PC feature. The result gets little use, because someone opening a phone in a lift, on a factory floor or at a client site can do very different things from someone at a desk.\u003C\u002Fp>\n\u003Ch2>Ask about context first\u003C\u002Fh2>\n\u003Cp>What are the three things users do most on mobile? Usually checking status, approving simple items and uploading photos.\u003C\u002Fp>\n\u003Cp>Which actions become dangerous on a phone? Bulk deletion, complex configuration and amount changes should be restricted or double-confirmed.\u003C\u002Fp>\n\u003Cp>What is the network like? Factories and warehouses often have poor signal, so offline buffering and automatic retry matter.\u003C\u002Fp>\n\u003Ch2>Design trade-offs\u003C\u002Fh2>\n\u003Cp>Keep only high-frequency actions on the first screen and push the rest deeper, rather than stuffing the whole PC menu into a drawer.\u003C\u002Fp>\n\u003Cp>List items should carry enough detail to decide without opening them.\u003C\u002Fp>\n\u003Cp>Keep forms short: scan instead of typing, default instead of choosing.\u003C\u002Fp>\n\u003Cp>Mobile is not a shrunken admin panel; it is a second product for a specific context. Understand the context and the feature list follows.\u003C\u002Fp>","","blue","佳益方圆团队","2026-04-18T16:15:00+08:00",1,false,[16,17,18],"Mobile","Context","Product Design",{"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","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","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","Observability: Logs, Metrics and Traces","When something breaks, answering 'what happened' is worth more than 'the system is slow'.","teal","2026-04-20T16:15:00+08:00",[38,39,40],"Observability","Logs","Operations",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":10,"kind":26,"sortOrder":46,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","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","Retrospective: A Regression That Slipped Through","One unrelated change brought back a bug fixed three months earlier.","cyan","2026-04-16T16:15:00+08:00",[55,56,57],"Retrospective","Testing","Quality",{"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","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","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","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[73,74,75],"Requirements","Product","Risk",{"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":13,"featured":14,"tags":83,"category":85},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[84,18],"Industry Products",{"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","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","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}]