hartlco
hartlco

Icro 2.2 for iOS and macOS is now available in the App Stores. 8h from submission to release for both platforms. 🙌

|
Embed
manton
manton

@hartlco Congrats on the release!

|
Embed
vincent
vincent

@hartlco congrats 🥳 Pretty great turnaround from them!

|
Embed
mdhughes
mdhughes

@hartlco Pretty unpleased by the new UI. Hard to get to conversations (teeny invisible dots and then tap again on mystery meat icons), doesn't fill in timeline gaps.

|
Embed
hartlco
hartlco

@mdhughes The long-press actions are still there like in the previous version. The dots just enable yet another way to access the action items. What is your suggestion for those action when wanting to avoid the typical swipe cell actions?

|
Embed
In reply to
hartlco
hartlco

@mdhughes Regarding the timeline gap issue: I would appreciate an issue on Github with more detail or by mail.

|
Embed
mdhughes
mdhughes

@hartlco Long-press doesn't have conversation view, just share/reply/fave. But left-swipe is good, it's the obvious action to see more.

|
Embed
mdhughes
mdhughes

@hartlco There may not be a gap, just quiet time, but I can't tell because now it zooms me to the top instead of letting me load more and scroll up.

|
Embed
hartlco
hartlco

@mdhughes Good point about the conversation view, I'm going to add it in a bug fix. I might consider bringing the swipe-actions back, thank you for your feedback!

|
Embed
mdhughes
mdhughes

@hartlco Thank you!

|
Embed
dejus
dejus

@hartlco @mdhughes +1 on dissatisfaction with with access to the conversation view. Now two taps instead of one. Adding it to the contextual menu might help, though still two taps.

I'd also suggest moving the ellipsis from below the text to below the time.

Also, I notice that tapping anywhere in the cell other than the text shows the action buttons, but I'd suggest tapping the text (if not a link) should also do that, i.e. tapping anywhere in the cell that isn't a link or image should toggle the action buttons.

And a swipe to conversation would be nice. Perhaps emulate Tweetbot: swipe right-to-left to show the conversation, swipe left-to-right to reply. (Just a swipe-and-go, not swipe-and-tap-button.)

(Icro is still my favorite app for Micro.blog.)

|
Embed
mcg
mcg

@hartlco Since there is no UI that lets you know if a post has any replies, I am constantly using the 3 dots/conversation action. I would love a faster way to get to conversation view. Swipe left or just a tap?

|
Embed
mcg
mcg

@hartlco I have noticed gaps here. Icro is the only client that reliably holds read position and doesn't miss posts.

|
Embed
mcg
mcg

@hartlco have not noticed gaps here. Auto-correct fail.

|
Embed
hartlco
hartlco

@mcg Ah, that's great to hear. I'll work to bring back the swipe gestures in some form as well!

|
Embed
hartlco
hartlco

@dejus Thank you so much for the feedback! It really convinced me to revisit the topic again. I hope to bring improvements to the beta builds in the coming days.

|
Embed
joec
joec

@dejus @hartlco Pushing everything to a contextual menu was the number one reason I stopped using Icro on iPhone and iPad. (I still use it on Mac.) I find it infuriatingly slow to use contextual menus for anything but very infrequent tasks.

+1 to bringing in swipes. They are so ingrained at this point from Twitter apps that they are just muscle memory at this point. And they are so much faster for quick actions like conversation and replying.

Also, I don’t feel hiding the buttons behind a … button is necessary. It’s not like they take up a tremendous amount of room. But if we had swipes for the two most frequent needs (convo and reply) I could live with that.

|
Embed
dejus
dejus

@joec @hartlco Agreed. It's fine to have sharing and favoriting in those more indirect menus, since I don't use those often, but replying and viewing the conversation are the two most common operations, so need to be easier to access. Following the example of the third-party Twitter apps makes sense. Or even the way the official Twitter app does it: I don't use it often, but it appears there you simply tap the message to see the conversation, with a reply field at the bottom. It does make sense to see the whole conversation when replying; I often want to see what other people have said, or refer to multiple people. The Twitter app gets a lot wrong, but I like that.

While tweaking this area, another request: automatically include all @ mentions, or perhaps have a button next to the Link and Image ones to include them, or do username auto-complete, or something. For example, in this reply I had to manually type "@hartlco" despite replying to a message to both.

|
Embed
Avancee
Avancee

@hartlco Have to agree with others in the critique of losing the gestures, and using multiple tabs in order to do what was a single tab previously.

Gestures, and a secondary action of tap and hold, are the more prevalent interactions. Yes, they could be definitely an improvement with discoverability. That seems to be what you are addressing with the triple dots. However, that pattern is very obscure to both android and iOS. It's definitely a different mental shift, even if the resulting action is familiar.

There's no kind of indicator that a reply was part of a wider conversation (I see a few of the clients missing on this, this is not specific to this app). It's also not clear where in the conversation you are replying (also not specific to this app).

Some positive feedback: definitely much more reasonable than it was in previous versions. This does not seem like the San Francisco dark font. But that just could be my eyes at the moment. Speed actually seems a little bit better as well. But that could also be getting used to it again.

Gonna follow this thread here; as well as take a few more days to just get familiar again with the changes. Change is not a bad thing; there's usually a reason why design takes a leap the way it does. It's my day job to make change via design. Am a bit more patient than I used to be with bits like this.

|
Embed
hartlco
hartlco

@dejus @joec I added the conversation and reply swipe actions in the latest beta. Username-autocomplete I high on my list as it annoys me a lot as well! Again, thank you all for the feedback!

|
Embed
hartlco
hartlco

@Avancee Thank you so much for the feedback. I introduced the swipe gestures in the latest beta. I'm close to getting rid of the dots completely and just migrating fully to the swipe-actions.

|
Embed
chrispederick
chrispederick

@hartlco Thank you for the swipe actions! 🙌

|
Embed
Avancee
Avancee

@hartlco 👍🏾

|
Embed
joec
joec

@hartlco Awesome. Thanks for considering our suggestions. This feels so much better already. I think I may be switching back to Icro full time.

|
Embed
dejus
dejus

@hartlco Much better, thank you.

|
Embed
dejus
dejus

@hartlco Did you get my TestFlight feedback? It doesn't indicate that it was sent, which doesn't inspire confidence.

|
Embed
dejus
dejus

@hartlco One point I made, that I'll repeat here for others to possibly weigh in on: I still like my suggestion of including a reply field in the chat view, so the whole conversation can be reviewed. I’d argue that there’s no need for a separate modal reply view. Just go to Chat to read the conversation and/or reply.

|
Embed
hartlco
hartlco

@dejus Nothing arrived in my inbox but I can see it in the dev portal, thank you! +1 for the renaming to "chat". The left-swipe gesture is already there and should be working. If not, it's a bug 😂 I'm going to explore you suggestion with the in-line reply. Can't promise anything but it's definitely interesting!

|
Embed
dejus
dejus

@hartlco More beta feedback in the portal for you, on Load More.

|
Embed
hartlco
hartlco

@dejus Fully agree with you on the loading state inside the Load more cell. I tracked it as an issue in GitHub. I was experiment with loading more content without user interaction but never managed to achieve a a great experience because of the loading times. Maybe it's also time to revisit this again.

|
Embed
dejus
dejus

@hartlco Please do. Automatically loading more when reaching the top or bottom of loaded posts would be much more convenient. You could simply display a bar with an activity indicator and "Loading..." message to show that it is doing something. (I added a comment to the GitHub issue.)

|
Embed