Thank you for making this app! It feels like an adequate alternative to liftoff, but I am having some (usability) problems. Could be a “me”-problem, though, since I am still getting the hang of the app and also the wall of settings it provides.

  • I cannot subscribe to any community. The button does vanish for a split second but just reappears. Tried it on multiple, but never worked.
  • I am using the left-handed setting. But the “preview” popup of a link has the buttons inconveniently on the right.
  • I can’t find out to jump to “all” or “local” posts of a specific instance.
  • Up/downvotes are on the left, but comment count on the right. Would be cool, if there was an option to have them together.
  • default up/downvote color is inverted from my point of view (up is red, down is blue). Would be cool, if there was a simple switch button without having to pick the opposite colors manually.
  • Drafts are saved but I can’t find them. A menu in the composing-post would be cool.
  • Something else, I currently can’t remember.

Thank you!

Edit: oh, it would be cool, if “save post” could be pulled out from the submenu beneath a post or comment.

Edit2:

  • the community-popup (button on top left) has a weird “back”-history. A popup should be always first to close. Also it should be modal since you interact with everything in the background and can’t close it tapping outside.
  • settings are weirdly bugged if you return from a category back to main. If i use the button on top left, everything works. But when I use the system back button, I cannot click on any category anymore. Though, I can still scroll.
  • Nithanim@programming.devOP
    2·
    10 months ago

    Thank you!

    The app doesn’t handle tablets very well at the moment

    I am not really sure what you mean because I am pretty satisfied how everything works, actually. I am mostly just stumbling over weird things and just wrote them down :D It was just a bit annoying to reach to the back button instead of touching outside the popup.

    I veeery shortly tried out the rail nav but I am not sure. I have not missed the vertical space to be completely honest. But I am testing it out some more, I think. Alsoooooo, after changing this setting, the navbar becomes unusable xD

    • idunnololz@lemmy.worldM
      2·
      10 months ago

      Oh no. What do you mean by the nav bar becomes unusable? If the setting enables correctly the navbar should be hidden in favor of the nav rail. Do you mean the nav rail doesn’t respond to taps?

      • Nithanim@programming.devOP
        2·
        10 months ago

        Sorry! So from a user perspective, the navbar just moves, sorry for the confusion. The switch between normal and rail mode works. And both modes work. But when I change the setting in a way that makes the bars switch, any of them stops working. Meaning, the buttons are interactable and theey switch their active state, but their action is not triggered. Restarting the app fixes it.

        Example:

        1. Be on Home page
        2. Go to settings
        3. Set rail from off to on (or reversed)
        4. Tap on inbox (or saved, …)
        5. Active button changes (the highlight showing on what page we are) but the page is not changed (we stay on the home page and do not navigate to the inbox)

        Also, I found out (I think) that when writing a comment, and in the middle switching to another app and then closing summit, does not save a draft. I assume, you only save drafts when navigating inside the app and do not check that. I mean I did not expect it to, just letting you know.

        • idunnololz@lemmy.worldM
          2·
          10 months ago

          Thank you for reporting the bug with the nav rail setting. This will be fixed in the next update.

          As for the draft issue, swiping an app away is generally considered “force quit” so the system doesn’t allow the app to handle this sort of event in any way. The upside to this is that you can kill any app even if they misbehave or are malicious however it also means apps cannot save their state if you kill them in this way.

          This is just a long way of saying that this isn’t a bug with the app and the app behaves as expected.

          • Nithanim@programming.devOPEnglish
            2·
            10 months ago

            Well shit, I didn’t know that. It has been a long time since I touched Android dev and also never needed that knowledge.

            One app I rarely use, uses some event that is triggered when it goes to the background or whatever. As soon as the app leaves the foreground, it shows the “saved” toast. It works both with the home button for the “desktop” and also when using the “open apps” switch UI (whatever that is called). Of course that is a step before the force close and is more complex to to handle for you since the editor window is not closed.

            Thank you for putting up with my shit xD