Topic
Apps and app stores
When a system needs an app, what changes for it to work offline, and the App Store and Google Play rules: account, commission and distribution.

Why TestFlight is not a way to distribute your company's app
TestFlight is Apple's testing tool: each build lasts 90 days and then becomes unavailable to whoever installed it, so it cannot be the way your team uses an app every day. The right channel depends on who uses the app. A public app goes to the store; your own team's app goes to the store behind a login the company provides, or ships as a private or unlisted app; an app built for a client company ships as a private app for that organization, on Apple and on Google. Apple's Enterprise Program is not a shortcut: it requires 100 or more employees and is for internal use only.
13 min read
13 min read

When your app pays a commission to Apple and Google, and when it can charge outside the store
An app pays the store a commission when it sells something digital that people use inside it, such as a subscription, content or an unlocked feature; physical services, live consultations between two people and free apps that accompany a paid web system charge outside the store, with no commission. In Brazil, since June 2026, Apple charges 21% plus a 5% processing fee on purchases through its system, and still takes a commission when digital content is paid for outside it. The most expensive mistake is mixing, in the same app, what is exempt with what is not.
16 min read
16 min read

Mobile app or web system: how to decide what goes on the phone
The question is answered per user profile, not for the whole system. An app makes sense for people who work away from a desk and need what only an app does well: keep working with no signal, talk to a device over Bluetooth, use location with the screen off. Whoever manages the system, uses it now and then or arrives through a link stays on the web. In our projects that have an app, the web system keeps doing everything and the app handles only the field work: at Beckers, the technician fills in the report in an Android app and the office reads everything in the web system.
16 min read
16 min read

Who owns the App Store account: you or the company building your app
Owning the app is three things decided in three different places: the code, in the contract; the store listing, in the developer account; and the ability to ship the next version, in the signing certificates — and whoever controls the account controls the product. What matters isn't which account the app is born in, but which account it ends up in, whether yours started being opened on day one, and whether the migration is a planned step in the contract. We've run that full cycle: the transfer preserves ratings and your installed base, and it breaks specific things that need to be mapped beforehand.
16 min read
16 min read

What changes in a system when the app has to work with no signal
Offline-first is not an app feature: it is a decision that changes the database, the server and the product scope — above all, what does not go onto the device. And an app that promises offline and freezes is worse than an honestly online one: the difference between the two lives in details that almost never show up in a proposal. Almost every write the server later rejects is a rule the app did not know, and the first fix is to move that rule into the app.
19 min read
19 min read