AquaMail Forum
English - Android => Development builds => Topic started by: Nadejda Fudulska, MobiSystems, AquaMail support on April 28, 2017, 04:38:02 pm
-
https://www.aqua-mail.com/download/AquaMail-market-1.9.0-351-stable-6866329d5cc3.apk
--
The update is currently visible from 50% of all devices, randomly picked by Google
+ Exchange: Contacts sync (with Contacts app).
+ Updated design: Message view and new "Add Аccount" screen
+ Updated design: navigation drawer is now over the window title (Material Design).
--
Обновление пока видно с 50% устройств, выбранных Google в случайном порядке.
+ Exchange: синхронизация контактов (с приложением Контакты).
+ Обновлённый дизайн: добавление учётной записи, отображение сообщений.
+ Обновлённый дизайн: боковая панель теперь поверх заголовка окна (Материальный Дизайн).
-
Hello,
do you mean 1.9.0-315 or 1.9.0-351?
How is your Sytem from Beta to stable Google?
Is everything <351 in the Version 351?
Are the changes in 348 in this Version...?
Thank you for clarifying,
Thomas
-
Hello,
I am sorry, my mistake, I mean 1.9.0-351. Yes, the changes from 1.9.0-348 are included in this version.
Nadia
-
Does this version remove the ability to reflow on resizing?
If so, why is it not mentioned in the release notes?
-
Does this version remove the ability to reflow on resizing?
Yes.
If so, why is it not mentioned in the release notes?
Because if we do mention it, then everyone and his brother will immediately complain to support, rate the app 1-star, etc.
Are there going to be any complains without us mentioning? How many people will actually notice?
We'll know soon enough, but let's not nudge people towards complaining.
-
Re: - the notification icon for individual notifications (the first 5 ones) should be a single (not a double) icon
Um, no.
Re: - Color of grouped notifications ("10 more...") should be orange (account color in the screenshot) - and not like it's displayed currently
Thanks, fixed (on the "next" version branch).
-
It is better as it is now than before. As a user, I prefer the way it zooms now without changing the message structure/view
No, it is emphatically not better. It may be better for YOU, but you cannot generalise that.
-
Because if we do mention it, then everyone and his brother will immediately complain to support, rate the app 1-star, etc.
"Let's remove some functionality from our paid-for application, but we won't tell anybody and hope that they don't notice"
That's a disingenuous (not to say dishonest) thing to do. Is this how MobiSystems do business???
-
Hello,
on my Galaxy S7 I never see the floating context bar?
Not in portrait, not in landscape.
Android 6.0.1
Thank you very much,
Thomas
-
I certainly hope the author realizes deletion of features is not the right way to do this. Give users the option to opt into the new method or keep the old. More advanced users know to backup an app (titaniumbackup) before accepting updates. I certainly do this. Release change loge are usually incomplete - just look at google apps - bug fixes and performance improvements. What does this really mean....
-
Hello,
on my Galaxy S7 I never see the floating context bar?
Not in portrait, not in landscape.
Android 6.0.1
Thank you very much,
Thomas
The floating bar appears when selecting a message in Message list.
To enable it, app settings - Look and feel (there's a setting to tick)
I set the option. I didn't know that it is only by a selected mail in message list. I thougt in message view, too.
Thank you very much,
Thomas
-
It is better as it is now than before. As a user, I prefer the way it zooms now without changing the message structure/view
No, it is emphatically not better. It may be better for YOU, but you cannot generalise that.
I've been trying to search the forum for the details on this change. Does this mean that if you resize the message content with two-finger pinching it will not reformat the text so that it re-flows within the new area dimensions? And that you may now need to horizontally scroll to view text that did not re-flow?
-
Because if we do mention it, then everyone and his brother will immediately complain to support, rate the app 1-star, etc.
"Let's remove some functionality from our paid-for application, but we won't tell anybody and hope that they don't notice"
That's a disingenuous (not to say dishonest) thing to do. Is this how MobiSystems do business???
I think Philip makes a good point.
-
It is better as it is now than before. As a user, I prefer the way it zooms now without changing the message structure/view
No, it is emphatically not better. It may be better for YOU, but you cannot generalise that.
I've been trying to search the forum for the details on this change. Does this mean that if you resize the message content with two-finger pinching it will not reformat the text so that it re-flows within the new area dimensions? And that you may now need to horizontally scroll to view text that did not re-flow?
Question answered - update was just installed. My fears were confirmed. I can't imagine why AM would be changed to work this way. Too bad.
-
Because if we do mention it, then everyone and his brother will immediately complain to support, rate the app 1-star, etc.
"Let's remove some functionality from our paid-for application, but we won't tell anybody and hope that they don't notice"
That's a disingenuous (not to say dishonest) thing to do. Is this how MobiSystems do business???
Unbelievable! How can the development team justify removal of an essential feature - then opt not to include that detail in test builds or the change log! This will prompt a Google Play review. Not 1-star but certainly strong words for this (apparent knowing) omission.
Why not add an option to enable/disable reflow?
-
Hello,
what I do not understand regarding reflow discussion.
It was programmed in the past in a complex manner and made available in the software. Now it was removed from the source code. An option would have been a minimal effort.
It would be different if it had to be programmed.
With most emails I see no big difference. For some, the old procedure is better, for the others are the new one.
Otherwise, software is further developed and can not be customized for everyone.
That must be accepted.
Microsoft, for example, not everyone has switched to Vista ...
Many Thanks, Thomas
-
It is better as it is now than before. As a user, I prefer the way it zooms now without changing the message structure/view
No, it is emphatically not better. It may be better for YOU, but you cannot generalise that.
I've been trying to search the forum for the details on this change. Does this mean that if you resize the message content with two-finger pinching it will not reformat the text so that it re-flows within the new area dimensions? And that you may now need to horizontally scroll to view text that did not re-flow?
Um, I realized the new behavior and my first thought was: It must be a bug in Android's web view (recently updated from Play Store).
if it is actually a conscious change in AM's app code, then it's a limitation of usability and IMHO actually no improvement.
-
Given the way this was rolled out (no advance notice; intentional omission from change log; defending latter on the basis of not driving negative ratings in Play Store..really?) my view is this is an irreversible executive decision made on 'mount high' on behalf of ignorant an user base who clearly can't think for themselves and don't recognize good design when they see it. Thank you for saving us from ourselves by not providing a toggle that would reenable auch a horrible UI and thus present a distressing UX that might drive negative Play Store ratings. After all, that's what it's all about - 5 star nervana.
-
Re: Given the way this was rolled out (no advance notice
What do you mean "no advance notice"?
There was advance notice, here, on the forum, in development builds, with discussions on pros vs. cons, including a detailed explanation (by yours truly) about why this change was necessary and is an improvement (IMO).
And there are users who did agree - and those who didn't obviously.
Perhaps you wish for some kind of "advance notice" on Play? There is no such thing. A "what's new in this release" goes with an actual version update.
It is possible to edit the "description" in Play, but who's going to read this, seriously?
So this forum *is* the place where:
- We post "development" (work in progress) builds
- There is someone (myself) who often explains changes / features / etc. in depth
- There are direct user-to-developer discussions happening all the time
Speaking of "corporate things", does Outlook or TypeMail have anything like it?
Re: intentional omission from change log
Yes. Because if you tell people that you've changed (removed) something - they'll start complaining -- even if they wouldn't have even noticed otherwise.
That's just psychology, and has nothing to do with "way of doing business" etc.
So we actually want to see how many users will notice without us telling them "hey look, we removed something".
Re: Thank you for saving us from ourselves by not providing a toggle that would reenable auch a horrible UI and thus present a distressing UX
The trouble with "more and more" settings is their poor discover-ability.
---
And I'll say it again:
The actual change is "avoid scroll jumping that happens if you reflow on zoom" and we got complaints about that jump all the time.
There is no more jumping, it's now actually possible to zoom in "something".
-
Kostya wrote:
So this forum *is* the place where:
- We post "development" (work in progress) builds
- There is someone (myself) who often explains changes / features / etc. in depth
- There are direct user-to-developer discussions happening all the time
Speaking of "corporate things", does Outlook or TypeMail have anything like it?
I don't know if those other businesses provide the same level of communication; likely not since you have suggested that they don't. Regardless, this forum and your participation in it is, I think, quite uncommon and greatly appreciated.
Kostya wrote:
Re: intentional omission from change log
Yes. Because if you tell people that you've changed (removed) something - they'll start complaining -- even if they wouldn't have even noticed otherwise.
I believe this "Shhh, don't say anything and maybe they won't notice" approach to feature changes is misguided. It suggests that you (and/or Mobi I suppose) are trying to sneak changes into the app that may be unexpected and controversial. It gives the impression, to me at least, that you're unsure of and not committed to the benefit of the change. Unless you are considering a career change I think your talents are wasted on trying to manage user psychology.
Kostya wrote:
The trouble with "more and more" settings is their poor discover-ability.
I think that AquaMail has long since passed the point where the number of settings is an issue. Just think, a search feature has been added to the settings screen to assist us. It is right to look long and hard at adding new settings options, especially for new features. But in cases where long-time functions are modified and no longer work the same, and the change is likely to be controversial, as is this re-flow change, then a setting may well be worth considering.
-
Re: Given the way this was rolled out (no advance notice
What do you mean "no advance notice"?
There was advance notice, here, on the forum, in development builds, with discussions on pros vs. cons, including a detailed explanation (by yours truly) about why this change was necessary and is an improvement (IMO).
And there are users who did agree - and those who didn't obviously.
Perhaps you wish for some kind of "advance notice" on Play? There is no such thing. A "what's new in this release" goes with an actual version update.
It is possible to edit the "description" in Play, but who's going to read this, seriously?
So this forum *is* the place where:
- We post "development" (work in progress) builds
- There is someone (myself) who often explains changes / features / etc. in depth
- There are direct user-to-developer discussions happening all the time
Speaking of "corporate things", does Outlook or TypeMail have anything like it?
Re: intentional omission from change log
Yes. Because if you tell people that you've changed (removed) something - they'll start complaining -- even if they wouldn't have even noticed otherwise.
That's just psychology, and has nothing to do with "way of doing business" etc.
So we actually want to see how many users will notice without us telling them "hey look, we removed something".
Re: Thank you for saving us from ourselves by not providing a toggle that would reenable auch a horrible UI and thus present a distressing UX
The trouble with "more and more" settings is their poor discover-ability.
---
And I'll say it again:
The actual change is "avoid scroll jumping that happens if you reflow on zoom" and we got complaints about that jump all the time.
There is no more jumping, it's now actually possible to zoom in "something".
Hard to argue against this rational as it is self serving and thus largely impenetrable. Unless one follows this thread religiously subtle changes can go unnoticed among the background noise. As a Google Play beta tester I received notice of an update and (as always) scanned the change log for recent developments. Since only 'popular' changes are now being included that no longer serves as a reliable communication medium. I've seen developers take this path - only tell the user community a filtered version of reality, in particular omitting items that may lead to negative ratings. Hopefully this is a one off; likely I have missed other changes that were deamed too unpopular to publish.
-
Actually I'm not sure if this change made it into any of the "beta" releases on Google Play.
-
Actually I'm not sure if this change made it into any of the "beta" releases on Google Play.
It did as that's where I acquired 351 (Google Play).
-
@Kostya Can we expect to see this feature turn in the next beta?
If not, is it safe to downgrade the apk of an older version after updating to current?
-
Thank you all for your valuable feedback. We are monitoring it but we have not made the decision yet.
-
Nadejda, please see my post about this issue in a different thread
https://www.aqua-mail.com/forum/index.php?topic=5669.msg34392#msg34392
I hope your monitoring will result in the right decision. Thank you!
D.N.
-
Nadejda, please see my post about this issue in a different thread
https://www.aqua-mail.com/forum/index.php?topic=5669.msg34392#msg34392
I hope your monitoring will result in the right decision. Thank you!
D.N.
+1(00) 💯
Thanks @AquaJet for your feedback
-
I have to agree with AquaJet as well.
In every other respect AquaMail is the best Android mail client that I have used, but this change is a deal breaker for me, and despite the time and effort I have put in to configuring it, if the change is not reversed (or made an option), then I'll have to find a different mail client.
-
I have to agree with AquaJet as well.
In every other respect AquaMail is the best Android mail client that I have used, but this change is a deal breaker for me, and despite the time and effort I have put in to configuring it, if the change is not reversed (or made an option), then I'll have to find a different mail client.
Just a question (I'm not discussing your request).
Do you happen to know another email app that does reflow after zooming in?
I honestly don't know; I have yet to do the research and hence my comment about having to find another mail client.
However, even if I find that such a thing does not exist, then I'm afraid that I would still move. I would rather use a mail client that never claimed to have a particular feature, than one which had it (in a paid version, to boot) and then removed it, especially when the removal was deliberately and cynically omitted from the change log.
What confidence can I have that other useful features won't get get removed from AquaMail in the future?
-
However, even if I find that such a thing does not exist, then I'm afraid that I would still move. I would rather use a mail client that never claimed to have a particular feature, than one which had it (in a paid version, to boot) and then removed it, especially when the removal was deliberately and cynically omitted from the change log.
What confidence can I have that other useful features won't get get removed from AquaMail in the future?
"That's it!.." (https://goo.gl/SC4Vhw)
;)
-
Thank you all for your valuable feedback. We are monitoring it but we have not made the decision yet.
After a week or so without this key feature it is still missed. It would seem an option to enable/disable in message view is the best choice, even if the former is imperfect (I can live with scroll jumping).
As an aside, text reflow is the main reason I use the Opera web browser on Android and is often cited in reviews as a decision critera over Chrome (same underlying engine).
-
Thank you all for your valuable feedback. We are monitoring it but we have not made the decision yet.
After a week or so without this key feature it is still missed. It would seem an option to enable/disable in message view is the best choice, even if the former is imperfect (I can live with scroll jumping).
As an aside, text reflow is the main reason I use the Opera web browser on Android and is often cited in reviews as a decision critera over Chrome (same underlying engine).
I second this suggestion to implement "rewrap text" (after 'zoom-in') as an option.
For me - personally - it's really annoying to need to scroll right / left to be able to read the whole text after zoom into the message.
-
After a week or so without this key feature it is still missed. It would seem an option to enable/disable in message view is the best choice, even if the former is imperfect (I can live with scroll jumping).
As an aside, text reflow is the main reason I use the Opera web browser on Android and is often cited in reviews as a decision critera over Chrome (same underlying engine).
Ditto! (on all the statements above)
I also primarily (~98%) use Opera on my phone (I use Chrome only when Wi-Fi sign-in fails in Opera).
-
Not only does opera have functioning text reflow, but also seems to be very fast at rendering pages.
-
Hi, let's distuingish between "pinch-to-zoom" and increasing font size by using volume buttons or menu.
Personally I'm fine using the volume buttons to make text size bigger. And text reflow works like a charm.
When using "pinch-to-zoom", the text reflow does not work anymore. And it seems to be difficult to implement this without having the "jump issue" (if I understood correctly).
Suggestion:
You know, that we have a configurable button bar in message view. Maybe we could have two buttons there to increase/decrease size the same way the volume buttons do?
Maybe the complaining people would like and use it instead of "pinch-to-zoom"...?
-
Hi, let's distuingish between "pinch-to-zoom" and increasing font size by using volume buttons or menu.
Personally I'm fine using the volume buttons to make text size bigger. And text reflow works like a charm.
When using "pinch-to-zoom", the text reflow does not work anymore. And it seems to be difficult to implement this without having the "jump issue" (if I understood correctly).
Suggestion:
You know, that we have a configurable button bar in message view. Maybe we could have two buttons there to increase/decrease size the same way the volume buttons do?
Maybe the complaining people would like and use it instead of "pinch-to-zoom"...?
This is an interesting workaround! I was aware of menu/volume button zoom functionality (actually used them regularly on another device) but hadn't tried it recently. I works quite nicely on my current mobile where the volume buttons fall naturally under thumb. My daily driver is a slate with buttons inconveniently positioned on the rear; need to work with that for a few days to see if becomes more natural while processing mail. On a third device I remapped the physical volume buttons w/Xposed (long story); a more accessible menu/button bar option in AquaMail would probably work there.
It would still be nice to see reflow on pinch zoom become an option within message view settings. However, it would be disingenuous to say the priority remains the same following @nica's enlightening comments... at least for me.
As an aside, I hope the MobiSystems takes this as a constructive learning for future releases. In as much as possible promote a positive perspective (eg: viable workarounds) when a feature is removed for cause vs. intentionally omitting it from the change log hoping no one notices. The latter really rubbed me the wrong way.
-
Hi, let's distuingish between "pinch-to-zoom" and increasing font size by using volume buttons or menu.
Indeed, they are not the same.
And one big advantage of "pinch-to-zoom" is that it works on both text and images. So, if a message contains both that one wants to "enlarge to make legible", you don't need to fiddle with two ways of controlling the effective zoom.
Yet another advantage of using pinch-to-zoom is that is it is the same as in Opera. And pinch-to-zoom exists in most image-viewing apps. It also exists in a bunch of other apps that deal with text reading (albeit in many cases without reflow). So, it is a standard mechanism implemented by many apps across mobile platforms for zooming in on both images and text.
That makes it a pity that a definite strength (but obviously not quite recognized by Kostya and/or MobiSystems as such) of Aquamail gets abandoned this way.
Personally I'm fine using the volume buttons to make text size bigger. And text reflow works like a charm.
....
Suggestion:
You know, that we have a configurable button bar in message view. Maybe we could have two buttons there to increase/decrease size the same way the volume buttons do?
Maybe the complaining people would like and use it instead of "pinch-to-zoom"...?
Nica, you may or may not have seen it in an earlier thread on this issue: Kostya reminded about the volume keys (which I've been using as well), and I responded. Indeed, that functionality is helpful in some cases. But in some messages, increasing font size results in the overlap of the lines. No line overlap occurs in case of "pinch-to-zoom".
I just looked at a bunch of the recent messages (on the phone with the pre-change version), and all of these messages where fonts overlap work well with "pinch-to-zoom", and with most of them, reflow works nicely.
For the gurus and curious, here is an example of the HTML that is used in such messages:
<td width="560" align="left" valign="top"
style="padding:15px 20px 0px; font-family:Arial, Helvetica, sans-serif;
font-size:14px; line-height:18px; color:#58585a; font-weight:normal;"
class="lr04">
This email is to inform you that your account
information has been updated. If you did not initiate this change, please
<a
href="..." target="_blank" style="color:#0068b3; font-weight:normal;
text-decoration:underline;">click here</a> or contact us at
<a href="tel:1-800-KRO-GERS"
alias="Footer:1-800-KRO-GERS" target="_blank" style="color:#0068b3;
font-weight:normal; text-decoration:underline;">1-800-KRO-GERS</a>.
</td>
Obviously, in this short example the text reflow is not overly important, I am just using it to illustrate the HTML code where "pinch-to-zoom" works, but the volume buttons - not. While I do not consider this style of e-mail message coding being a good one, unfortunately, there is an appreciable volume of such messages.
When using "pinch-to-zoom", the text reflow does not work anymore. And it seems to be difficult to implement this without having the "jump issue" (if I understood correctly).
Based on the responses of people who chimed in here about the "reflow" issue, - all these people are happy to live with the "jump issue". So, an option that enables one and disables the other is an obvious solution, since the code for the functionality already exists. (I feel as a broken record, repeating what several people have suggested already). And so far no reason was offered why this toggle option would be a problem.
Well, actually, I think I know the reason, and understand MobiSystem's hesitation to re-enable it: it might be hard to explain to many "unsuspecting" users that if they experience the jump, they need to disable reflow, and vice versa. And if it is not re-enabled, the new users will not know that they could've had something better. So, there might be less headache to deal with if MobiSystems withstand this initial wave of complaints.
However, a carefully worded option item can work; setting its default value to the "new" behavior: no reflow/reduced jump [with a warning: "changing this may create focus jumping when you are zooming"] would reduce potential for the complaints from the users.
But for those people who know and who are used to the reflow functionality, it's a pity if it will be thrown away. (And as I've written before, and as acknowledged by Kostya, this "jump issue" is not eliminated completely, just significantly reduced.)
Personally, I don't want to waste any more time on this issue, as I don't think any of my further comments would help the cause. (I am just still hoping Kostya and MobiSystems will make the right decision.)
@Kostya: I'd like to point out that I haven't seen many people celebrating in these forums or in the comments on Google Play (I just looked there), the improvement for the "jump issue". (And I very much doubt you've received many e-mails with the praise for that, have you?)
But there are complaints about the lack of reflow.
-
Re: font-size:14px; line-height:18px
That's the issue right here -- this hardcodes line height, so when we make an adjustment to font-size, the line-height stays the same -> overlap.
https://developer.android.com/reference/android/webkit/WebSettings.html#setTextZoom(int)
There is no function to adjust "line height".
Which just again goes to show:
- the best situation is when HTML messages are deliberately made to look nice on mobile devices.
- which is not difficult: the CSS Media Queries tech has been around for a while, and there are quite a few "mobile HTML frameworks" for both web pages and email messages.
https://www.google.ru/search?q=html+email+mobile+template
12,000,000 results.
First result is titled "Top 25 Free Responsive HTML Email Templates 2016" - *twenty five* on that page alone.
And I'l reiterate, this is not an AquaMail specific technology rather it's a universal, official, widespread web standard.
- when that's not the case, any attempt to do this on the client is "putting a square peg through a round hole" and may end up with unwanted artifacts.
Re: I haven't seen many people celebrating in these forums or in the comments on Google Play (I just looked there), the improvement for the "jump issue"
Why would there be? But there are no complaints (about "scroll jump") anymore, and no questions about "why am I unable to zoom in on an embedded image".
Besides, message view with auto-fit -- for the first time ever -- looks absolutely perfect:
- has same-sized margins on both sides
- the *whole* message is inside those margins
- and, a nice side effect, swiping from message to message can be done with one gesture not two ("swipe to scroll to the end of the message's width then swipe again to actually go to next message").
-
Re: font-size:14px; line-height:18px
That's the issue right here -- this hardcodes line height, so when we make an adjustment to font-size, the line-height stays the same -> overlap.
https://developer.android.com/reference/android/webkit/WebSettings.html#setTextZoom(int)
There is no function to adjust "line height".
Yes, I know that the hardcoded line height is the problem. But apparently some software used by too many people is generating that HTML for e-mail messages. Who will teach those "authors"?
But my point wasn't about that. What is important here is that pinch-to-zoom+reflow have been working mostly fine with that.
Re: I haven't seen many people celebrating in these forums or in the comments on Google Play (I just looked there), the improvement for the "jump issue"
Why would there be? But there are no complaints (about "scroll jump") anymore, and no questions about "why am I unable to zoom in on an embedded image".
That was my followup response to your comment about people not talking about importance of reflow before that was removed. ("Everything was just fine.")
- and, a nice side effect, swiping from message to message can be done with one gesture not two ("swipe to scroll to the end of the message's width then swipe again to actually go to next message").
As I've written before, while describing my impressions about this new version, that side effect is actually a problem. Since you are now forced to scroll horizontally (after zooming in), - it's overly easy to jump to the next message.
(A couple of times, being surprised that I am on a different message, I've even jumped to the 2nd next message, in which case the position in the e-mail I was reading was lost. But that's just an aside.)
Besides, message view with auto-fit -- for the first time ever -- looks absolutely perfect:
That's nice, but in this context, that's like a surgeon telling a patient after the surgery: "Sorry, we cut off the wrong leg, but the good news is: we figured out that we actually can cure the other leg..." ::)
(And yes, removal of this feature feels as a removal of ... maybe not a limb, but a finger. And the argument that there are 9 more left is not a helpful consolation. It is still painful.)
The key point that you are carefully avoiding in all your responses is that those good things (improved "non-jumping" and reflow upon pinch-to-zoom) do not have to be completely mutually exclusive (despite the visible conflict between the two): in the previous post above, I clearly outlined how the "toggle-switch" option with the defaults to the new behavior could make everybody happy.
At this point, these arguments on your side indicate that you've already made your mind about the issue (hence the "confirmation bias" (https://en.wikipedia.org/wiki/Confirmation_bias)). So, there is no point for me to waste any more of time on this issue, - yours and mine.
For the record: Even though "the missing finger" hurts, Aqua Mail remains a great app, despite this reduced functionality. (And it still has plenty of great features to spare 8) ) And I still have utmost admiration and appreciation for the work that you've been doing both in development and support.
-
Re: I haven't seen many people celebrating in these forums or in the comments on Google Play (I just looked there), the improvement for the "jump issue"
Why would there be? But there are no complaints (about "scroll jump") anymore, and no questions about "why am I unable to zoom in on an embedded image".
Besides, message view with auto-fit -- for the first time ever -- looks absolutely perfect:
- has same-sized margins on both sides
- the *whole* message is inside those margins
- and, a nice side effect, swiping from message to message can be done with one gesture not two ("swipe to scroll to the end of the message's width then swipe again to actually go to next message").
Pretty clear you have strong passions around this issue given the manner in which it was publicly communicated (not) and ongoing defense of the indefensible. Yes, content creators bear some responsibility but the world is an imperfect place and imperfectly constructed emails will be part of the real-world landscape for the foreseeable future.
Auto-fit is not the nirvana it is purported to be as it regularly distorts embedded images from mainstream sources. I have it disabled on several devices and pinch-shrink ~5-10% of incoming items to eliminate overflow on run-of-the-mill 7" 320 PPI panels. Fortunately, the required reduction is rather small (perhaps 10%) so accompanying text reflow typically is not an issue in this context given normal email margins.
I do not take issue with the new default as the characteristics quoted above are clearly beneficial to mainstream users who value aesthetics over functional flexibility (which is the primary AquaMail differentiator IMHO). The workaround that was discussed during 351 development and recently republished by @nica softens the blow. Too bad it wasn't included in the change log.
Like @StR [re: "Personally, I don't want to waste any more time on this issue, as I don't think any of my further comments would help the cause. (I am just still hoping Kostya and MobiSystems will make the right decision.)] I grow tired of the dialog as the decision has clearly been made to substitute one imperfect solution with another imperfect solution based on personal preference while disregarding commonly accepted transparency practices. That's a headwind no one can counter.
-
I came to this forum to express my impression from the recent update, but I see that several people have told that already.
Thank you, StR and Davey126 for formulating my concerns and new problems due to the lack of reflow.
Please, give us an option to enable reflow after zooming.
Thank you!
-
I guess, there is another complaint about the 'missing text reflow after zoom-in':
https://www.aqua-mail.com/forum/index.php?topic=5688.new#new
-
Add me to the list of people that want the text zoom back to the old way. I'm extremely disappointed that it wast taken out and not even mentioned in the Google Play new features area. On top of that I have found the comments from the original creator of this application to be quite condescending. I put up with the analytics being put in secretly (and then thankfully allowing us to turn it off) and the Material Design change, which took me a few weeks to get used to (and I'm OK with it now). But I am tired of this. It is still a great app and support has always been fantastic. But ever since MobiSystems took over it's been a complete and utter mess.
If the reflow option is not put back I will leave as I don't have the time or energy to keep reading this forum on what should be an application that I use constantly and just works. I don't want to check more options, I don't want to have to re-do my entire look and feel every time the app is updated. I beg you, please stop with all these changes. Or give us AquaMail Classic or something like that.
The text zoom/reflow is a big deal to me. I'm over 50 and the eyes ain't what they used to be sadly.
Thanks for listening at least,
Steve