Thank you for the chance to comment on the integrated function vs plugin situation.
Please bear in mind that I'm only a new user of AquaMail,so I'm not up to speed on all the past history.
I'm more than happy for the aforementioned functionality to be integrated into the app, including the additional filesize that will accompany such a decision.
As I see it, core/key functionality that is to be expected of an (email) app should rightly be integrated into the app itself.
For those extras however, non-core, yet useful, additions could be placed into a single, separate plug-in. This single plugin could house all current and future additions and features, and allow only those users who are interested in said features to opt-in (for the additional resource cost: size, etc).
This would keep the main app as slim and core-featured as reasonably possible, while not preventing more 'exotic' (yet reasonable) functionality for those who require it.
Having a single plug-in (which houses all extras) might also make (future) development easier (once the initial plugin framework was included).
[I'm not a dev, so I admit that I have no idea how difficult implementing a plugin system would be, nor if it would be worth the effort]
Regards,
J