Original Summary

I've been building a learning app for 3–8 year olds (letters, tracing, counting, drawing, read-aloud stories). It's on the App Store, and I've just pushed the Android build to closed testing. Both platforms come from one Swift codebase using Skip in native mode — SwiftUI compiles to Compose rather than running in a web-view. The interesting part is where the two diverge, which is never where you expect: An accessibility label broke the Android build for three weeks and nobody noticed, because CI only ran the iOS legs. SwiftUI takes a String there; the Android bridge only takes Text . Text fields looked wrong on Android for months. SwiftUI renders a bare field; the Android side rendered Material's outlined box inside the rounded pill I'd drawn around it. Two different apps, one codebase. My release bundle shipped 45MB of debug symbols per library. The strip task ran on every build and changed nothing, silently, because the Gradle plugin had pinned an NDK version that wasn't installed and the property it sets wins over the path. Fixing it took the download from 55MB to 37MB. Icons are the other trap: unmapped SF Symbols don't fail the build, they just draw an error triangle on Android, so a symbol table and a screenshot check are the only defence. Happy to answer anything about the Skip side — it's a small enough ecosystem that most of this isn't written down anywhere. If you've got an Android phone and two minutes, I also need 12 testers to unlock production, which is the part I hadn't budgeted for: https://play.google.com/apps/testing/com.pawan.alphabetadventure   submitted by   /u/Diligent_System_6100 [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/27 00:20:28