Sorry for the delayed response: this thread has sprang very quickly, while I was traveling.
1. One has to keep in mind that the size that Kostya mentioned (5-6 MB) is the packed, and not installed one. The latest Google Play version installed on my phone weighs 9.52 MB, as reported by the system (Settings -> apps).
It is still a very reasonable size. In comparison, the behemoth Chrome unpacks from 31 MB
to 99 MB, and because it is a part of the bloatware installed on my phone by Verizon, I have no way uninstalling it without rooting the device. (In reality, it takes 112 MB, because you cannot stop it, and the moment it starts, it stores 13 MB of data. Deleting that data doesn't last for too long: some seconds or minutes.)
2. Some users do have "the latest and greatest" phone models, but some people do not. E.g. I have Droid Razr M that I am mostly happy with (it is compact and does what I need). But it has only 8 GB of memory built in, and Motorola/Verizon modified system that doesn't installed allow apps to be installed on the external SD card (even those that are app2sd). Also, some apps and parts of the system are hardwired to save their information on the internal storage, and cannot be configured otherwise (e.g. screenshot, file download, ...)
Because of how Android handles the internal space (or how it is configured on this phone), - essentially only about 4-5 GB is allocated to apps and storage.
Some of my associates are using cheap budget-type "Made-in-China" phones with probably 4 GB (if not 2 GB?) of internal storage, and then the space is even more valuable.
I do have a 32 GB miniSD card - I store all the photos and videos there, and move the files there whenever I can.
I am keeping the OS version on 4.1.2, avoid the update to 4.4.x (KitKat), - for a combination of reasons, including the limitations with respect to the SD usage/permissions.
I do have a bunch of apps installed: web-browsers, navigation (Google Map, Waze), travel (TripAdvisor, Kayak, Yelp, "My" airlines), communication (Skype, Viber), developmental games for my kid (reading, math, etc. - those are usually large, 20-50 MB each). Together with the preinstalled bloatware that is disabled but cannot be deleted, they take close to 3.5 GB.
As a results, the "available" space (for the system and apps) varies from about 460MB (when the OS starts complaining about being short on storage and that some functions might not be available) to 600 MB, - depending on how much space is used by cache and data. When I am doing an update for the larger apps (e.g. TripAdvisor), - I must clean all the cache, to have sufficient space for the update to be installed (downloaded apk, overhead space [unpacked app or whatever it is?]).
The nice thing about Aquamail is that I can update it without much hassle with the storage space.If and when I need to install some new app, I must maintain the space balance, and usually delete some apps that are not used frequently.
For all these reasons, - I am happy that Aquamail has a very modest footprint.
3. Image shrinking functionality.
I think it is a good feature (that some of my correspondents would benefit from, - but then again, many of them are not using Aquamail). However, I'd like to warn about the potential evil side of it: Some iPhone users do not realize that the images they send are reduced in size. Just recently on the photography list that I read, there was an issue that a guy was receiving pics of his recently born grandchildren at the reduced resolution that was marginally [in]sufficient for printing, and his daughter had no clue about that. And, of course she had no idea how to send the original image.
And earlier, I've heard about someone else, who assumed that the images were preserved in the e-mail that he sent to himself, and deleted the originals.
I hope, Kostya, these two stories would be helpful in how you will design the configuration of the image-resizing options.
4. Personally, I am happy with the functionality that QuickPic offers for resizing.
So, for me, the convenient option would've been to have the same type of "filter" for attachment that presently exists for the inline image, -- namely, opening the image(s) in QuickPic and configuring how it should be resized. Unfortunately, AFAIK, QuickPic doesn't offer "batch-resizing" option. (As a reference, - imageMagick library does that type of job well on Unix, but I haven't tried its port on Android)
I am not 100% sure if I'd be installing that option for Aquamail or not, - it depends on the implementation/functionality. So, for the flexibility of not installing it if I don't need it, - I'd vote to have it as a plug-in.
5. Just in case, - I've seen an app (Tiny Flashlight + LED) where the developer decided to go modular, with the plugins after some long period of time of having his (rather popular) app. That did make the base app small in size. (And I appreciated it, as the original app was rather large in size). But the change broke what people got used to. As a result, there were quite a few whiners who were unhappy, giving ultimatums in the feedback. After just a few months he switched back, to an all-in-one app. (I didn't update it.)
The moral of the story: people are happy to be unhappy with seemingly drastic changes, no matter what.
6. I agree with others (Pyler, ..) - who proposed this functionality to be an option in the settings menu that calls for plug-in to be installed.
Kostya, I hope these thoughts are helpful to you in making the decision(s).
PS. And yes, please, make the font BukaZyaka size 9.82 available.
(In plain-text mode, of course! Please!)
