Arctic is a (much) better Lemmy client than any other out there for iOS at least but there are some nifty features for the most recommended app Voyager like the ability to disable side swipes altogether because Apollo’s (reddit) double-tap to upvote for example is much intuitive where side swipes are used to enter and exit communities, posts, comments, menus, settings… or whole app together on Android or Jailbroken devices.

This is my multireddit link after removing u/user which were included as r/_u/redditor from an existing bug to test this for Arctic which would fully enable me along with a lot of us to leave Voyager behind.

  • CreatureSurvive@lemmy.worldM
    0·
    3 months ago

    Great feedback. I’ve already implemented a way to disable swipe gestures which will be included in the next release. This is something I added the other day to improve the navigation on MacOS, but I’ll also include it in the iOS builds.

    The double tap/long press for voting is a good idea, I’ll look into adding this as an option to the gesture settings.

    Adding a subreddit migrator should be very easy to implement. I’ve already implemented the Lemmy Explorer api, which should streamline the migrator. I could probably come up with a working migrator tomorrow morning.

    • Avieshek@lemmy.worldOPEnglish
      0·
      3 months ago

      If you’re the developer of this app, then I would like to clearly state myself directly:

      1. Don’t get me wrong, Side Gestures should actually exist but it’s overly if not weirdly misused in Lemmy. Side Gestures should be strictly utilised to quickly enter (right swipe) and exit (left swipe) communities, posts, threads or menus including in settings by default instead of having to tap some corner of the screen. Side Gestures can also be used to switch between All-Hot-Recent in the homescreen which honestly is like hidden for average users.
      2. Double-Tap should be utilised to upvote, Long-Press to collapse comments, Haptic Touch to show the expanded menu items instead of accidentally triggering something random every time.
      3. ‘Save’ followed by ‘Share’ should have a dedicated button to the right under posts while the ‘voting’ and ‘comment’ button on the left need to become larger instead of having a case of ants vs elephants for the same function.

      ↑420 ↓69 <gap> 💬 <gap> ✓ ⥯

      1. The ••• menu for each post shouldn’t then display the same repeated options like the voting buttons for the third time after the above implementations and instead should focus on highlighting the essentials with focused minimalism like save media for example.
      2. Comment threads are really hard to follow on Lemmy, the colours are a nice touch that may even evolve to change with lighter shades but replies under main comments need to stay single like reddit with lines guiding them. Having the same card layout for comments, replies, subreplies… for the entire thread is a chaotic disaster. This goes same with posts where it’s difficult to gather where the screenshot ends and the caption begins especially when the attachments here are also weird.
      3. The display of user thumbnails would be really appreciated in the comments thread so not only it has some life but it’s easier to identify individual participants without being forced to read each meaningless to complex random usernames while scrolling.
      4. It’s been also observed that one can’t create or manage communities from the Lemmy client as opposed to Apollo which became moderator’s favourite Reddit client.

      A personal observation: Default theme colour shouldn’t be sleep inducing bland blue but something warmer even if red to reddit’s orange. Skype, Facebook, Twitter to AIM all started with that particular shade of blue which didn’t have OLED darkmode back then; it’s advisable to not start with grey-blue combo to red-black by default for all age group going in this era.

      • CreatureSurvive@lemmy.worldM
        0·
        2 months ago

        Yes I am the developer of Arctic, thank you for taking the time to write out your thoughts. I’ll do my best to respond to all your feedback here.

        1. Swipe Gesture: when I mentioned a new feature to disable swipe gestures I was only referring to swipe actions on cells, eg. (upvote, downvote, reply, share, etc) swipe navigation is still enabled when disabling swipe actions. However with swipe actions enabled, you can still use swipe gestures to navigate the app, you just have to start your swipe at the edge of the screen just like navigation in the Mail app for instance. With that said, based on this feedback I added a new setting to enable full-screen navigation gestures, with this you can swipe left or right to go forward or back from anywhere on the screen. This is not a default iOS navigation gesture which is why I did not opt to include this from the start.
        2. Tap Gestures: This one I am unsure about, double tap to upvote makes sense, however Long Press, and Haptic Touch are the same thing on most devices now that Force Touch was removed from new devices, and there would be no good way to handle both on the same view. I’m not sure I understand what you mean by triggering something random every time? Do you mean swipe gestures are random?
        3. Post Footers: currently the information on the bottom left of the posts is just statistics label, its meant as an overview of the post contents, not as an interactive element, that is why the label is small, since interaction is not intended. As for the vote buttons to the right, I could definitely make the configurable like the swipe actions so you could configure their actions. I’d prefer not to use the left information label as buttons, but I can look into adding more customization to this footer view as a whole.
        4. The ••• menu: This is something I may be able to improve. I’ve opted to show repeated options like voting so the menu is consistent throughout the app. Users can change the swipe actions, and disable vote buttons, etc. so this menu may be the only place with those options left available, and I wanted that to be consistent in post feeds, open posts, comments, etc.
        5. Comment Threads: This is something that definitely has room for improvement. I am working on adding profile pictures which should help improve following conversations. I do not want to differentiate between comments, replies, subreplies, etc. These are all just comments whether it is a reply to the post or a parent comment. I do plan to add support for continuous lines to the left to make it easier to follow comment depth, However the current layout is basically the standard as far as comment feeds are handled in most other apps I’ve used with comment chains.
        6. Comment Profile Pictures: I mentioned this above, but this is something I am working on adding, I’ll hopefully have this included in the next update.
        7. Creating and Managing Communities: This is a feature already, Though I may need to improve its visibility. For editing a community you moderate, you can open the ••• menu at the top of the screen when viewing a community feed and select Edit Community. Here you can edit the community metadata and settings. For managing user reports, you can open the same menu and open the Mod Zone (only available if you moderate at least one community) which is available in the profile tab, or the subscriptions list view. For creating communities, currently this is only available in the profile tab under the ••• menu, but I will also be adding this to the subscriptions feed for better visibility.
        8. Default Tint Color: This one is something that won’t be changing. Arctic is modeled to behave and appear like a system app on iOS, most system apps use a default tint color of blue. Additionally, Arctic’s logo is primarily blue and this fits with Arctic’s branding. Blue is also a calming color with great contrast and legibility with both light and dark backgrounds. In designing Arctic, my primary influences were Apollo, and the system Mail app, both of which use the default system blue for the tint color. However, if you do not care for the default tint, you can always change it in Arctic’s Appearance settings. I am also in the process of adding full theming support for Arctic so you can customize the color scheme of basically every element in the app, and save multiple themes.

        All of this is open to discussion, I’m always happy to add new features and improve Arctic. On that note, I did finish up the Reddit Migrator yesterday. The new migrator works almost exactly the same as the migrator in Voyager, It was done very well there and I did not see much room for improvement.

        Thank you for all the feedback, it is always welcome!

        • Avieshek@lemmy.worldOPEnglish
          0·
          2 months ago

          I am glad and nice to meet you, after witnessing your dedication first hand I would also like try my part in bringing more exposure to your client here on forward and I hope my feedback can also bring forth the same support from others. If it’s preferable, we can directly interact in DMs to keep tab of everything at one place and would be happy to contribute.

          1. Only exiting an app itself is not default on iOS with side swipe gestures but for navigating through different layers of menu has been standard for ages including the Reddit app itself. The swipe actions on cells is something more seen on email clients like Spark or Mail itself if not Gmail but there’s a huge difference between public comment threads and your inbox, this is something more suitable for chats or messages.
          2. I was only introducing the idea to see past through existing implementation of repeated taps where you may even implement triple tap for example to collapse comments or use the same haptic touch to open the menu and then select the collapse option at one go without lifting your thumb as has been recently being explored by Threads and Instagram app beautifully. Am sure am not the only one (I have read quite a thread of user annoyances on support forums regarding this) but the default behaviour of swipe gestures lead to random upvote-downvote, archive to block triggers - this is the numero uno 1 complaint of all Lemmy users and am only saved by drawer style offered by Arctic however it still adds friction. Voyager only sparingly addressed this by adding a toggle to disable side gestures but without an alternative at place like the double tap I have suggested that exists from Reddit to Instagram. If your app is the one that properly addresses the feedback I bring forth to you which are the the no. 1 complaints of users transitioning to Lemmy then this can easily become the no. 1 client to the point of setting how things (like default behaviour) should be at Lemmy after Voyager.
          3. There’s no use in configuring the ones on the right if the left ones are a non-interactive element, can’t they made to be interactive? I don’t mind if the voting buttons are on the right but my point was to integrate both interactive and non-interactive element into one and open up space to lessen the weight of ••• for common actions.
          4. That’s why the implementation of earlier is important as in a step-by-step process, there’s no third-step without second-step in place.
          5. Simply make it easier to differentiate posts from the comments, the captions and attachments in the posts, and the parent comment from another parent comment so it isn’t confusing with replies if two people are arguing and am only interested in reading about the topic on hand for example.
          6. Thank you.
          7. I actually aware where the edit option for communities are but unlike the desktop site for Lemmy.World, if your description has more than three lines on the viewable pane making use of the 5000 word limit with community rules, headers, bullet numbering etc then you’d understand what am to talk about. Simply try to put and then edit your previous reply am responding upon in a community description through your client.
          8. I will not argue on this and rather suggest exploring different hue of blue like your app icon at least and match the comment thread colour with the theme they’ve opted like Fiery Red should be automatically implemented if that the theme they enabled.