[{"data":1,"prerenderedAt":285},["ShallowReactive",2],{"blog-post-en-qr-menu-kafe-vakasi":3,"blog-siblings-en-qr-menu-kafe-vakasi":102},{"id":4,"title":5,"author":6,"body":7,"category":85,"cover":86,"date":87,"description":88,"draft":89,"extension":90,"meta":91,"navigation":92,"path":93,"readingTime":94,"seo":95,"stem":96,"tags":97,"__hash__":101},"blog_en\u002Fen\u002Fblog\u002Fqr-menu-kafe-vakasi.md","A café's switch to QR menu: 90 days later","Codifya",{"type":8,"value":9,"toc":76},"minimark",[10,14,37,40,45,48,52,55,59,66,69,73],[11,12,13],"p",{},"In March, a single-location café in Konya switched to QR Menu. Ninety days in, here's what they shared:",[15,16,17,25,31],"ul",{},[18,19,20,24],"li",{},[21,22,23],"strong",{},"90% drop"," in printed-menu cost (only the table cards get reprinted)",[18,26,27,30],{},[21,28,29],{},"60% fewer"," order errors from international customers (thanks to auto-translation)",[18,32,33,36],{},[21,34,35],{},"8 minutes saved per day"," on menu updates",[11,38,39],{},"More interesting than the numbers were the behavior shifts.",[41,42,44],"h2",{"id":43},"how-long-do-customers-stay-on-the-menu","How long do customers stay on the menu?",[11,46,47],{},"Average viewing time went from one minute to 2.5. We initially read this as a bad signal — longer might mean more indecision. According to surveys, the opposite was true: customers were now reviewing photos, checking allergen labels, and reading content details.",[41,49,51],{"id":50},"the-waiters-role-changed","The waiter's role changed",[11,53,54],{},"The pressure on the waiter to answer \"what do you recommend?\" eased, because the customer had already seen detailed info on the menu. That freed the waiter to focus on table atmosphere and service.",[41,56,58],{"id":57},"the-unexpectedly-popular-feature","The unexpectedly popular feature",[11,60,61,62,65],{},"The owner did not predict that ",[21,63,64],{},"stock-based auto-hiding"," would matter most. Sold-out items quietly disappear from the menu — the customer orders, the waiter never has to apologize.",[11,67,68],{},"That single detail meaningfully improved customer satisfaction.",[41,70,72],{"id":71},"takeaway","Takeaway",[11,74,75],{},"Switching to QR menu isn't just a paper-to-digital migration. Done right, it's an infrastructure that reduces operational load and errors while quietly improving the customer experience.",{"title":77,"searchDepth":78,"depth":78,"links":79},"",3,[80,82,83,84],{"id":43,"depth":81,"text":44},2,{"id":50,"depth":81,"text":51},{"id":57,"depth":81,"text":58},{"id":71,"depth":81,"text":72},"QR Menü",null,"2026-03-30","What changed for a single-location café after switching to QR Menu? A short case study on operations, customer behavior, and error rate.",false,"md",{},true,"\u002Fen\u002Fblog\u002Fqr-menu-kafe-vakasi",5,{"title":5,"description":88},"en\u002Fblog\u002Fqr-menu-kafe-vakasi",[98,99,100],"case study","restaurant","operations","6ZxiVmPuaiJF0I3FvOYwjKItZUX8Lo9I6id0kwBEQlY",{"prev":103,"next":184},{"id":104,"title":105,"author":6,"body":106,"category":172,"cover":86,"date":173,"description":174,"draft":89,"extension":90,"meta":175,"navigation":92,"path":176,"readingTime":177,"seo":178,"stem":179,"tags":180,"__hash__":183},"blog_en\u002Fen\u002Fblog\u002Fcityos-40000-reports-case.md","CityOS in a district of 180,000: 6 months, 40,000 tickets",{"type":8,"value":107,"toc":166},[108,111,115,118,121,125,128,131,135,138,144,150,156,160,163],[11,109,110],{},"In January 2026, a district in Antalya deployed CityOS. By June, over 40,000 reports had been received and resolved. Beyond the numbers, the most valuable lessons from this period:",[41,112,114],{"id":113},"process-first-software-second","Process first, software second",[11,116,117],{},"The mayor's first question in the initial meeting wasn't about software features: \"How do we not reduce the permanent staff count?\" This was the right question. If they'd adopted CityOS just to \"collect reports faster,\" it would have been the same as the old system.",[11,119,120],{},"The solution: instead of an agent chasing reports, build a team that meets reports in the field. 12 street representatives in the city center, each responsible for 4 neighborhoods. Every morning their mobile app shows daily routes.",[41,122,124],{"id":123},"finding-category-matters-more-than-volume","Finding: category matters more than volume",[11,126,127],{},"In the first two months, the top report type was \"pothole.\" An analysis revealed that 600 of 1,000 potholes were in the same heatmap — an area with heavy winter rainfall and old infrastructure.",[11,129,130],{},"When CityOS's reporting view started showing the mayor \"the source of the problem,\" it transformed from a routine request handler into a decision-support tool.",[41,132,134],{"id":133},"three-slowdown-points","Three slowdown points",[11,136,137],{},"As with any system, three points caused delays:",[11,139,140,143],{},[21,141,142],{},"1. Vehicle assignment:"," Directing a report to the field is the most critical step. Average wait time was 4 hours. A rotation algorithm was developed to bring this down to 90 minutes.",[11,145,146,149],{},[21,147,148],{},"2. Citizen feedback:"," There was no \"what happened\" response to the citizen who filed the report. A closed-loop notification was added: \"Your request was received → team dispatched → resolved.\"",[11,151,152,155],{},[21,153,154],{},"3. Neighborhood headmen (muhtars):"," The headmen were outside the system. After giving them read access, they started checking before complaints even arrived.",[41,157,159],{"id":158},"outcome","Outcome",[11,161,162],{},"Of 40,000 reports in 6 months, 94% were resolved within 14 days. The municipality's own data shows this was 61% in the old system. The difference wasn't in the technology; it was in how the team receiving reports was designed.",[11,164,165],{},"CityOS became a tool that helped the municipality rethink its own internal processes. The software didn't solve the problem — it made the problem visible.",{"title":77,"searchDepth":78,"depth":78,"links":167},[168,169,170,171],{"id":113,"depth":81,"text":114},{"id":123,"depth":81,"text":124},{"id":133,"depth":81,"text":134},{"id":158,"depth":81,"text":159},"CityOS","2026-04-20","How a district municipality managed 40,000 citizen reports in 6 months with CityOS. The design decisions that determined success — not the technology.",{},"\u002Fen\u002Fblog\u002Fcityos-40000-reports-case",7,{"title":105,"description":174},"en\u002Fblog\u002Fcityos-40000-reports-case",[98,181,182,100],"municipality","citizen engagement","Nd-D3hXbvFQLP_puK3e6rgBun6y2UllB94Ph5wgmAaI",{"id":185,"title":186,"author":6,"body":187,"category":272,"cover":86,"date":273,"description":274,"draft":89,"extension":90,"meta":275,"navigation":92,"path":276,"readingTime":277,"seo":278,"stem":279,"tags":280,"__hash__":284},"blog_en\u002Fen\u002Fblog\u002Fcodifya-vizyon-sade-mimari.md","Calm architecture: fewer concepts, fewer clicks, more outcomes",{"type":8,"value":188,"toc":266},[189,196,202,206,224,227,231,238,241,245,256,260,263],[11,190,191,192],{},"Over the years we noticed: the reason a user abandons an app is rarely a missing feature. More often it's the exhaustion of an interface that ",[193,194,195],"em",{},"does many things but explains none clearly.",[11,197,198,199],{},"At Codifya every product follows one principle: ",[21,200,201],{},"fewer concepts, fewer clicks, more outcomes.",[41,203,205],{"id":204},"fewer-concepts","\"Fewer concepts\"",[11,207,208,209,212,213,216,217,212,220,223],{},"The more new terms a user has to learn, the longer they feel like a beginner. In CityOS we use ",[193,210,211],{},"\"report\""," instead of ",[193,214,215],{},"\"ticket\""," and ",[193,218,219],{},"\"owner\"",[193,221,222],{},"\"agent\""," — because those words already exist in municipal vocabulary.",[11,225,226],{},"In FlowBit, terms like \"epic\" and \"story point\" are hidden by default. Teams that need them turn them on; most teams just look at \"task\" and \"sprint.\"",[41,228,230],{"id":229},"fewer-clicks","\"Fewer clicks\"",[11,232,233,234,237],{},"If a user takes four clicks to reach a goal, we look for the path to three. This is not about speed — it's about ",[193,235,236],{},"focus",". Every click is a small distracting decision.",[11,239,240],{},"In QR Menu, table number is auto-detected (embedded in the QR), language is auto-detected (from browser locale), and order confirmation is one tap. None of this is visible — but it's felt.",[41,242,244],{"id":243},"more-outcomes","\"More outcomes\"",[11,246,247,248,251,252,255],{},"Calm doesn't mean ",[193,249,250],{},"doing less","; it means ",[193,253,254],{},"appearing to do less",". The difference is in the infrastructure. BerberBul's booking system looks calm; behind it run conflict checks, auto-cancellations, and push reminders.",[41,257,259],{"id":258},"conclusion","Conclusion",[11,261,262],{},"A calm product comes from a calm architecture. A calm architecture is the byproduct of engineering culture: choosing the right abstraction, refusing unnecessary layers, and questioning every line of code.",[11,264,265],{},"Codifya's four products are the concrete expression of that culture.",{"title":77,"searchDepth":78,"depth":78,"links":267},[268,269,270,271],{"id":204,"depth":81,"text":205},{"id":229,"depth":81,"text":230},{"id":243,"depth":81,"text":244},{"id":258,"depth":81,"text":259},"Vizyon","2026-03-12","The principles behind every Codifya product. Calm is not an aesthetic preference — it's the precondition for sustainability.",{},"\u002Fen\u002Fblog\u002Fcodifya-vizyon-sade-mimari",6,{"title":186,"description":274},"en\u002Fblog\u002Fcodifya-vizyon-sade-mimari",[281,282,283],"design philosophy","simplicity","engineering culture","gOyTWPil0kftqVFgqXx5Hnf2_fgW3DWpGx61vqXOpkE",1781523775313]