/app-studio
App Studio map
A single-page explainer for how Turboexcel sequences platform decisions, automation, and store readiness. Use it as a conversation starter with your team before picking a cohort.
[platform_matrix]
Platform choices
We chart SwiftUI, Kotlin, Flutter, and React Native against your existing web skills, release cadence, and hardware budget. Native tracks win when store reviewers expect platform-specific behaviours; cross-platform wins when one team maintains parity across two storefronts with shared business logic.
- Device lab coverage: OLED burn-in checks, low-storage boot, regional carrier APN quirks.
- Designer pairing: token pipelines differ—Compose theming vs SwiftUI environment vs RN StyleSheet.
- Upgrade appetite: willingness to chase Xcode/Android Studio bumps vs pinning LTS channels.
// build_pipeline
Build pipeline
Starters ship with lint, format, and CI stubs. You promote artefacts through internal tracks before public store submission; mentors review YAML, not just app code.
git push → CI matrix (lint/unit) → artefact bucket → internal track → mentor sign-off → store draft/release_prep
Release preparation
Reviewer packets bundle behavioural notes, test accounts, and attachment indexes. We rehearse questions reviewers asked similar apps—not to promise outcomes, but to reduce vague replies.
