(no title)
knr2345 | 2 years ago
1. Reply button is below the sender's profile symbol in the thread message header.
2. Thank you for the feedback on activating the notification. This should work as anticipated but it's been quite some time since I received feedback related to notification behaviors so I'll certainly take a look.
3. Images and remote content are blocked by default (similar to Mail.app); clicking the 'photo' button (next to the Flag button) in the message header will reveal these images.
4. Expanding threads by clicking in thread message header white space would be a welcome addition and feature request. I'll add this to the planned feature list. Expansion via body content click will require a bit more investigation, however.
Appreciate the detailed feedback!
outcoldman|2 years ago
But at this point, I just don't see myself paying a subscription for an MVP/alpha product, with so many visible bugs, and not working (or not intuitive) basic features.
- Clicking a button for every message to see images is a weird decision, to be honest. I understand some people are more paranoid. But both Mail.app and Fastmail web client provide features for privacy to hide your IP for loading images. There are I guess some WebKit context menus, which suggest that I can download the image or open the image in a new window, and when I click it - nothing happens.
- You are right, there is a reply button. Just not where I expected it, considering I was expecting the same behavior/view as Mail.app. But even that - another bug / unexpected behavior - the reply email (From) chosen first from the list, but not the same email account that received the email. Say I received an email on support@example.com, and when I click Reply - the From account is selected to myaccount@fastmail.fm.
- I don't see any ability to attach inline images to messages. Drag and drop of the image from Finder to the Compose does not work. I see that I can attach documents to the messages, but don't see the ability to create inline messages.
So at this point. I already wasted a trial period to see that the state of the app in a very early alpha/beta. I would call it alpha because I believe there are many basic features are still missing. And it is definitely beta because some basic features don't even work, like lists don't update when I receive new emails.
I am sorry. It is just too early. I can't try again later in a few months, assuming you will release some updates soon. Which is very disappointing. I will give it another try, when I see it again, maybe mentioned somewhere else.
Really wish you actually had a TestFlight first to build the app to v1 and collect feedback. I do feel like there is a good potential of the app. And despite even that I really hate the subscription models, I went ahead and gave your app a try.