{"id":988591,"date":"2026-10-02T08:00:00","date_gmt":"2026-10-02T08:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988591"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"crash-free-sessions-what-founders-should-ask","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/crash-free-sessions-what-founders-should-ask\/","title":{"rendered":"Crash-Free Sessions: What Founders Should Ask"},"content":{"rendered":"
\n

Crash-free sessions is a stability ratio: sessions that did not crash, divided by sessions that ran. Founders should treat it as a question set, not as a trophy. Apple, a third-party SDK, and a hallway demo can all produce different numbers from the same week. This is the diligence list we use at Croncode<\/a> before we call a binary ready.<\/p>\n

\n

Ask how crash-free sessions are counted, who owns crash symbols, and which build the number comes from. A percentage without a method is a slide, not a gate.<\/p>\n<\/blockquote>\n

What does crash-free sessions actually measure?<\/h2>\n

A session usually starts when the app becomes active and ends after a period of background idle or a terminate. A crash is an unexpected exit the system or your reporter classifies as a crash. Force quit is not a crash. A watchdog kill might be. If two people argue about a percentage, they are often arguing about those definitions.<\/p>\n

Ask the studio to write the definition. Then ask which reporter they trust for the store gate: Xcode Organizer, MetricKit, or a vendor dashboard. Mixing them in one slide hides the fight. Shipping culture: how Croncode ships<\/a>.<\/p>\n

Which questions should you ask before you sign?<\/h2>\n
    \n
  1. Which build number is in the chart, TestFlight or App Store?<\/li>\n
  2. Are dSYMs uploaded automatically, and who has the Apple org that receives them?<\/li>\n
  3. How fast can you reproduce the top crash group on a device we name?<\/li>\n
  4. What is the kill rule for a crash that hits the first job?<\/li>\n
  5. Who reads the report on Monday, not only after a one-star review?<\/li>\n<\/ol>\n

    Account ownership belongs in that list. If symbols sit in a personal Apple ID, you will lose them when a contractor leaves. Write the owner now. Related: who owns the App Store account<\/a>. Hiring checks in this city: Istanbul diligence<\/a>.<\/p>\n

    When is a crash a product bug, not a device story?<\/h2>\n\n\n\n\n\n\n\n\n
    Signal<\/th>\nTreat as product<\/th>\nTreat as noise first<\/th>\n<\/tr>\n<\/thead>\n
    Same stack on two OS versions<\/td>\nYes<\/td>\nNo<\/td>\n<\/tr>\n
    One jailbroken device<\/td>\nNo<\/td>\nYes, isolate<\/td>\n<\/tr>\n
    Crash on the first job path<\/td>\nYes, block release<\/td>\nNever \u201clater\u201d<\/td>\n<\/tr>\n
    Crash in a rare locale string<\/td>\nYes, if you ship that locale<\/td>\nOnly if that locale is not-now<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Consumer jobs make this concrete. If YourStyle<\/a> died while saving a garment photo, that is a first-job crash. If Luviport<\/a> died while confirming a transfer window, same rule. A crash in a settings toggle you can live without is still a ticket. It is not a store blocker unless it is frequent.<\/p>\n

    How should a small studio report the number?<\/h2>\n

    Report seven and twenty-eight days. Name the build and the session count so a 100% on twelve sessions cannot pose as a launch metric. We do not publish invented crash-free rates. Do not accept invented rates from a vendor. Catalog: what Croncode builds<\/a>.<\/p>\n

    If the team is lean, one person owns the Monday read. Write the name. Hours: small team, multiple products<\/a>. Founder: Goktug Unver<\/a>. Co-founder: Yusufhan Sokur<\/a>.<\/p>\n

    What mistakes look like stability work?<\/h2>\n