The Computomatix Times

You find a bug. A typo on the paywall, a broken button, a copy fix that would take you 30 seconds to write. Then you remember: shipping it means a new build, a new submission, and days of waiting on Apple review.
That's the problem OTA (over-the-air) updates solve. Push a JS change, and it's live on people's phones within seconds — no review, no waiting. Here's my exact setup, config and all, so you can copy it instead of guessing.
I'm running this on Expo/React Native with EAS Update.
The core config
Two settings do almost all the work:
json
"updates": {
"url": "u.expo.dev/[your-project-id]",
"enabled": true,
"fallbackToCacheTimeout": 10000
}
fallbackToCacheTimeout: 10000 is the setting that actually matters. On a cold start, the app waits up to 10 seconds for a new update to download — and if one's there, it launches straight into it. The default is 0, which means any update only takes effect on the next cold start after this one. With the timeout set, updates land immediately instead of one launch late.
The trade-off is honest: on a slow connection, app start can take up to those 10 seconds longer. I've decided that's worth it — instant fixes over a slightly slower worst-case launch.
Remind the 10 seconds is a ceiling, not the norm. That's just the timeout if the download stalls. On a normal connection the update usually finishes in 1–3 seconds, so in practice you rarely feel any delay at all.
One thing to know: this only fires on a genuine cold start. Reopening the app from the background doesn't trigger a new check. Realistically though, barely anyone goes weeks or months without ever fully closing the app at least once — so in practice this basically never becomes a problem.
What actually goes over OTA — and what doesn't
OTA-able: anything in JS/TS. Screens, business logic, copy, navigation, images and other assets. If you can write it in your app code, it can ship instantly.
Needs a full store build: new native modules, version upgrades of native dependencies that touch native code, any app.json field that compiles into the native project (permissions, icons, splash screen — even the fallbackToCacheTimeout setting itself), and SDK upgrades.
One nuance worth knowing: sometimes a feature looks JS-only but only works because the native side already shipped support for it in an earlier build. A config or variable change can go out via OTA — but only because the native plumbing for it was already sitting in a build people already have installed.
The actual workflow
bash
npx eas-cli@latest update --branch production --message "description" --non-interactive
Then commit and push. One easy-to-miss detail: EAS Update publishes whatever's in your working directory right now — not your last commit. Uncommitted changes go out with the update whether you meant them to or not. So commit immediately after publishing, to keep git and what's actually live in sync.
Three more levers worth knowing about
Rollback. eas update:rollback reverts to a previous update, or all the way back to the bundle embedded in the original build. Your emergency lever if an OTA update breaks something in production.
Staged rollout. Updates can ship to a percentage of users first (--rollout-percentage) instead of going straight to 100%. I currently push straight to everyone — a staged rollout is the safer move for anything you're not fully sure about.
Code signing. Updates can be cryptographically signed so only bundles you authorized can install. Not essential for most solo setups, but worth knowing it exists.
Is this actually allowed by Apple?
Yes — with real limits, not a loophole.
Apple's guidelines technically say apps shouldn't download code that changes their features or functionality. But there's an explicit carve-out: code interpreted by JavaScriptCore or Hermes is fine, as long as it doesn't add native capabilities that bypass review. That's exactly what a React Native JS bundle is. The native layer never changes — your JS only calls into native functions that were already reviewed and approved when you submitted the build. This isn't a gray area workaround; it's the sanctioned case, and it's been standard practice since 2017.
What's inside the lines: bug fixes, copy changes, layout tweaks, feature flags toggling things that were already part of what Apple reviewed. What's not: hiding a genuinely new feature behind a remote flag and quietly switching it on later. That's the same interpreted-code mechanism, but it's used to ship something Apple never saw — and apps have been flagged for exactly that.
One honest caveat: review is policy plus judgment, not just the text of the guideline. No tool — not Expo, not any other OTA provider — can promise "Apple-approved" updates, because that certification doesn't exist. What does exist is a clear, long-standing precedent for this exact use case. Stay inside it (fixes and tweaks, not disguised new features) and you're on solid ground.
The short version
Set fallbackToCacheTimeo… continue on X ↗

This is how I use Grok Bot for Enterprise GTM at SpaceXAI.
When we were initially dogfooding this product internally, Grok Bot rapidly gained adoption throughout the company, and I created an internal Notion doc on how I use Grok Bot to share with my team. I wanted to share it externally if it's helpful for other GTM orgs setting up @bot .
Grok Bot feels different for me as it's not just a thinking partner, but I can trust it to go off and actually do things end-to-end. Every week it learns more about how I work, and gets sharper.
Tips for getting started
Make sure @bot is connected to what you leverage daily, ie: Salesforce, Gmail, Calendar, Sheets, Drive, Slack, Notion, Granola for meeting notes, Figma for slides, X, LinkedIn, your data warehouse and more.

Bot has its own computer that runs 24/7 so you can accomplish tasks while your laptop is shut.
Your bots have memory so will remember your preferences, and will learn your writing style. Ask bot to scan your gmail and slack for how you write.
One of my favorite ways to use bot is through the mobile app, and voice input so I can give bot tasks when I'm not at my computer. This makes putting together slides or pulling information from tools really convenient when I don't have access to my laptop.
Run your own team of bots

Chief of staff
My Chief of Staff owns meeting prep, inbox and post-call drafts, orchestrates the rest of the team. You can tell your chief of staff to spin up other agents, and organize your bots in sections. I like to pin my Chief of Staff as I use this bot most frequently.


Daily meeting prep
Tell your bot to create a routine to prep you for meetings for the day and pull from your tools (Salesforce, Gmail, Slack, Granola, Gong, or online research if it's a new meeting), I prefer a short, skimmable, output that I can read on my phone as I'm commuting to work. You can also have your bot create customized decks ahead of your calls for the day (it calls my slides bot).
Routines
Scan inbox and auto draft replies:

Automate follow-up drafts from Granola or Gong notes:

Prospecting bot
Builds pipeline gen plans, pulls intent data, does deep research (will watch webinars, listen to podcasts, find blog posts, scan LinkedIn/X for relevant posts). Customizes messaging based on company priorities and personal hooks, drafts in gmail, and puts together messaging in your voice. I like to run this overnight to have it ready in the morning.

Customer expert
One agent per strategic account (works for top prospects too). It watches the relevant Slack channels, digests calls, emails, and Slack threads, and runs a weekly media rundown on the account (relevant exec posts on X / LinkedIn, watches webinars, finds podcasts and blog posts). It also flags feature requests from calls, updates me on support tickets, and finds relevant new features for the customer.
Weekly media rundown:

Data analysis agent
I connect this to the relevant tools to track usage data across my book.
Product expert
I call this one "Cursor 10x engineer". An agent connected to the codebase for questions deeper than my product knowledge. When a customer asks something technical live on a call, I ask this agent and get a customer-facing answer back, and don't need to ask an engineer or dig through Slack, Notion, docs, etc. If you don't have repo access, an internal knowledge tool like Glean works as the source instead.
1:1 agent
Preps my weekly manager sync, I Granola our meetings so I can hand off tasks my manager and I discussed from our 1:1s and set up reminders.
Forecasting bot
Pulls from Granola, Gong, Slack, and email, and auto updates Salesforce opportunity notes. I give it the format I want the updates in, and this helps me streamline forecast calls and ensure my notes are constantly up to date.
Slides
My slides bot owns customer decks in Figma using our brand system and a master deck it maintains. It makes copies to customize per customer and even translates decks into other languages. Give the bot your design guidelines up front.
My favorite skill is to auto-update slides while I'm on a customer call, based on the Granola transcript.
Stop the Granola recording 5 or 10 minutes before the call ends and run it live, so you wrap up the call with a slide built from what the customer just told you during Discovery, or use it as a follow-up or opener for the next call.

Sales Coach
Have your bot watch your external calls on Gong, and give you feedback on what you could improve or what went well.
Helpful tips/skills
Onboard Grok Bot like a new teammate. The first time we do a task together, I ask the agent to record, take over the computer and demonstrate, then have it turn the recording into a skill. ie: I showed my bot how I like to research stakeholders on X.

Feed it your writing. Have it scan your sent mail and build a style profile before it drafts anything. Give your bot a few examples of outreach you're proud of.
Give your bot feedback and make rules for output… continue on X ↗