Did you actually build the app or did you just measure the size of the debug build?

WTF? I have been working on an app for quite some time now, I am running it as debug on my phone, and it is working quite well. Arey you guys telling me I won't be able to release it because it may be too large in file size?

-Go with app bundle it's version used with google play But in my opinion it's not logical the release be like 100 mp it's a game with a huge assets folder

I assume you've just built a debugger version.

If we are talking about Android sizes:

- A small app built in debug mode is about 176 MB and can be laggy on an older Android device.

- If you use split APKs for different abis, the app size is reduced to about 9–10 MB (https://docs.flutter.dev/deployment/android#build-an-apk).

- In production mode, the app uploaded to the Google Play Console is even smaller at 7.4 MB, but you need to build and upload an app bundle that's around 40-50 MB.

- After installation on a phone, the production version is about 18 MB, while your own build is about 22–24 MB.

* The "small app" has seven screens, a local database, and uses some native plugins and UI libraries. assets <500kb

check this docs https://docs.flutter.dev/perf/deferred-components

Maybe start by measuring the binary size? Because the source code folder on your Mac does not correspond to what the user downloads.

The compiler strips a lot of fluff out already.

Those pods probably don't take up that much space on users devices because of app thinning and bitcode. You can strip out extra architectures, assets and bitcode to get a more accurate attribution per pod. There are likely many faster ways to reduce your app size like optimizing images, enabling symbol stripping and deleting duplicate files. I made a tool to show you what contributes to app size and automates finding some of these quick savings: https://www.emergetools.com

If you’re trying to reduce app size, don’t use third party libraries. They’re full of 90% fluff you probably don’t even use. Take the ideas and build your own utilities. Compress images, look into On-Demand Resources, or load data from the network at runtime.

Maybe keep Crashlytics, but the default crash reporting is decent, and much less privacy invasive. Especially since in the fall you’ll be required to fill out a privacy disclosure for any new app release/update, which details exactly what info your app (or any of its included frameworks) gathers from your users device. So anything google/Facebook-owned will probably add a lot of disclosures, most of which are probably unrelated to your core app’s features.

First of all, Thanks everyone

But problem is still exist

The biggest piece of my app is a "Frameworks" folder

And as I told before most "heavier" pods are "Crashlitics", "DevToDev" and other important pods (around 40-50 Mb each)

I can't remove it or change with another one, cause need to see crashes in app and etc.

But how other apps use this frameworks and has just 30-40 Mb?

Ditch most of the libraries. I'm sure you can build the same app under 30Mb with the same functionality. Unless you have a lot of artwork.

Large apk size is due to building RN for all architectures (x86, x64, arm7, arm8)

You can reduce apk size by setting which target architectures you want in your eas.json

Don’t worry about that. When you’re deploying to the stores generate an aab or if you are using eas, expo will do that for you. After it’s published your app download size in the stores will be around 6 - 9mb

It's an apk, it will be big. An aab will be way smaller in size like maybe 10-20 MB or more based on app complexity and size.

its important an app is efficient, but small or large i dont see the problem. Who really looks at the size of an app to decide whether to download it or not? no one., and in fact there is a case to make about not wanting people who look at the size, they are either cheap or techy, not great customers.

The doc titled Understanding app size explains:

> Why is my app so big? > >It probably isn't, actually! When examining the resulting artifact of a release build for an app, it's common for developers who are unfamiliar with native Android and iOS development to be surprised by the file size — it's usually much larger than they would expect for an app if they were to download it from an app store. This is not the actual size of your app, which will be distributed on app stores! > > ... > > Typically, what app developers care about the "download size" on the Play Store (what the users see in the store listing when they go to download the app). This will be the size of the APK that Google Play generates from your AAB, which is tailored to the user's device. > > The only truly accurate way to see what your final app size will be shipped to users is to upload your app to the stores and download it on a physical device. Google Play also provides a reliable estimate for the expected download size on your developer dashboard.

Also, Google changed the default for a setting called extractNativeLibs which increases APK/AAB sizes to improve runtime performance.

> React Native 0.73 bumped the Android minSdkVersion to 23. This had the side effect of changing the default value of extractNativeLibs to false. > > If set to false, your native libraries are stored uncompressed in the APK. Although your APK might be larger, your application loads faster because the libraries load directly from the APK at runtime.

You can enable app optimization https://developer.android.com/topic/performance/app-optimization/enable-app-optimization

If min sdk is set to 30 or more I believe, you should enable legacy packaging.

I would first look at using apk analyzer to get a sense of what to go after. Don't include resources if they can be downloaded asynchronously, prefer vectors over images, enable app optimization to remove unnecessary code.

That .dll contains the C# projections for the WinRT APIs from the Windows SDK. It's pulled in automatically when you target -windows10.0.XXXXX.0 in your TFM.

You have three options:

• Remove the -windows10.0.XXXXX.0 TPM if you don't need it
• Enable trimming to reduce binary size (most will be trimmed)
• Stick with it

If you're on WPF, you might be out of luck.

Remove multi-language support. Seriously, try it and come back.

I guess if your machines already have the runtime installed you could use that. However keep in mind that you’ll have to ensure it is the correct version according to your application.

Maybe wasm could reduce it or DLL trimming?

If you don't bundle the runtime with the app, then you have to install and update it individually on every PC where the app runs.

Is there no deployment management tool used within the organization through which the SDK could be kept up to date as necessary on the workstations to meet your needs for your individual client users?

My initial impression is that, upon reinstalling, it's less than a gig because the media hasn't yet (fully) synced. If you have a large collection it's going to take up a large amount of space. That's probably not ultimately avoidable

Maybe you could reduce backup frequency in Anki preferences > backup. Other than that it should all be media and things right? Have you synced after reinstalling and it’s still that small?

Your suggested implementation is fine. It'd also help if you ever need to update your DB and refetch it from your app.

Android doesn't have native support for 7z compression. You'd need to bundle binaries in your app for support, which may defeat the purpose of saving bandwidth, depending on how large those binaries are.

I'd suggest just sticking with a zip file.

Previously, you would use obb for that, but now we uses play assets delivery. https://developer.android.com/guide/playcore/asset-delivery

1. Create rest API so that the backend can serve portions of the DB?

2. Use Google Play Asset Delivery

3. Use your own CDN and upon install ask for step of the user to download the DB in background

Can I ask what is stored in the database, without giving away sensitive information, that you need 110MB of space on every user's device?

Must you embed the db file? Can't you download it on first run?

...so are they basically killing compatibility for old apps ?

what do you have the “Archive Inactive Tabs” option set to?

12 gb is excessive. I only use arc on my phone, and my document and data is just over 1 GB.

How many downloads do you have under Files > On My iPhone > Arc Search > Downloads? I’d encourage you to double check to make sure there’s nothing located there

Holy smokes

https://preview.redd.it/8xdobaty277d1.jpeg?width=1170&format=pjpg&auto=webp&s=4f62ff5ed2453ea86ddaa1e9c5918f09dfb141ed

I’ve been using Arc Search since day one. Never reinstalled it. There’s clearly something wrong on your end 😅

Mine was at 1.5GB.
Cleared browsing data, removed downloads and archive. Now .2GB