What are APK and AAB files?
APK and AAB are the two file types an Android app comes in. An APK installs directly on a phone. An AAB is what you upload to Google Play, which then makes the right install for each phone.
APK: the file a phone installs
APK stands for Android Package. It is a single file holding everything the app needs. You can send one on WhatsApp or by email, and an Android phone can install it after the person allows installs from that source. That is handy for testing an app with your staff before it is on the store.
The downside is trust. Phones warn people before installing an app from outside the store, and customers are right to be careful. An APK is fine for your own team, not for the public.
AAB: the file Google Play wants
AAB stands for Android App Bundle. You cannot install it on a phone directly. You upload it to Google Play, and Play builds a smaller install for each kind of phone, so people download less. Google Play requires new apps to be uploaded as an AAB rather than an APK.
Which do you need?
For testing with a few people, an APK. For publishing on Google Play, an AAB, uploaded from your own Google Play developer account. Google charges a one-time registration fee for that account and checks your identity before you can publish.
Neither file matters to an iPhone. iPhone apps are a separate build that goes through Apple. If your customers use both kinds of phone, a web app at your own address works for everyone.
Read next
Build it for your business
Start with this example already written, and change every word to fit your business before you send it.
An Android app for my delivery staff: each driver signs in, sees today's deliveries in order, marks each one delivered with a photo, and I see progress on my phone.
You can build it and try it with free credits. To use it with real customers, you need a plan or a credit pack.