I’ve had enough of the text editing issue, where when you press backspace it highlights the space before the word and ends up deleting it. The developer passes off responsibility for this to the engine they use and seems to have no intention of addressing it.

What are the pros and cons of the other Android apps? I’m only considering ones on F-Droid, not the Play Store, so that rules out Summit and Boost. Ones I have available are:

  • Thunder (IzzyOnDroid)
  • Interstellar (IzzyOnDroid)
  • Voyager
  • Eternity
  • muffed (IzzyOnDroid)
  • Combustible
  • Hubi@feddit.org
    link
    fedilink
    arrow-up
    17
    ·
    22 days ago

    I’ve tried pretty much every app there is and ended up with Thunder. It’s got a huge amount of features and polish, a clean UI and gets regular updates. The only issue is that I don’t see the number of upvotes on posts since my home instance upgraded Lemmy, though that will probably get fixed soon.

  • manucode@infosec.pub
    link
    fedilink
    arrow-up
    15
    ·
    21 days ago

    I went from Jerboa to Eternity to Thunder. I liked Eternity a lot but it doesn’t get developed very actively which causes issues. Spoiler tags for example aren’t implemented correctly. Voyager seems to be great as well from all I have heard, but I don’t like its UI.

      • Evil_Shrubbery@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        21 days ago

        That’s why I support Eternity (and Infinity before that), but also use Voyager (I have a lot of others installed too, but they sleep).

  • squirrel@discuss.tchncs.de
    link
    fedilink
    arrow-up
    12
    ·
    22 days ago

    I went from Jerboa to Eternity to Raccoon to Voyager. I have to say Voyager is the most mature lemmy app when it comes to current features, development of new features, customizability and stability.

    • TWeaK@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      21 days ago

      Yeah others are saying it’s to do with the keyboard, or rather that other keyboards seem to get around the bug. However it’s only Jerboa that I have this issue with.

      I’m using the standard Android Keyboard (AOSP), so it’s not something you would expect to have errors. Don’t really want to change as I’m used to it and have it set up for different nationalities (Greek for maths, couple other countries for their funky accented letters).

      • ExtremeDullard@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        21 days ago

        Once you try swiping to type, you never want to go back. And OpenBoard has Greek letters of course. Honestly, give it a spin - regardless of your problem with Jerboa: I bet you’ll love it. Worst case, you’ll have wasted 10 minutes installing it, trying it out without success and uninstalling it 🙂

  • fisco™🇬🇧🇺🇦@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    22 days ago

    Muffed & Combustible, seem to be dead, Interstellar early development it seems & more geared towards Kbin… Eternity (very good) recently had a update after months of inactivity, whereas Voyager & Thunder (both excellent) have active devs and continuous support & updates…

    • TWeaK@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      21 days ago

      Looks like I’ll lean towards Voyager and Thunder, might give Eternity a go also. I had Voyager before but was sticking it out with Jerboa, we’ll see how I feel this time. Thanks!

      • fisco™🇬🇧🇺🇦@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        21 days ago

        You can’t really go wrong with either of those, I do lean towards Voyager as a personal preference… Raccoon is another that I really like, but I’m not sure if that will see any further development…🤷🏻‍♂️

  • Hadriscus@lemm.ee
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    21 days ago

    I’ve never had this happen, does it need a special set of circumstances?

    I get a similar glitch with all keyboards based on AOSP (openboard, etc), where pressing backspace randomly jumps back a few words

    I eventually switched back to swiftkey because it was unbearable

    • Treczoks@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      21 days ago

      I also have never seen that behavior. And even if, would it matter in any way how it handles the backspace key?

      • TWeaK@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        20 days ago

        It’s an absolute pain in the ass. When you press backspace once, the underline for autocorrect extends to the space before the word, then when you press it again it deletes the space, merging it with the word before. It will keep doing this over and over if you keep pressing backspace. You then have to go through and position the cursor just so in the middle of the word to add the spaces back - or, if you don’t notice it, you submit the comment and then have to edit it, which marks your comment and makes it dirty (lol, one thing I loved about reddit was the 3 minute leeway for edits).

        • Treczoks@lemmy.world
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          20 days ago

          I still fail to see that this is an issue. I use the backspace key only when I make a mistake. You seem to hang up the whole user experience of an app off it. Just make less mistakes that require you to use backspace.

          • TWeaK@lemm.eeOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            20 days ago

            I make little typos all the time, and often go back and edit things to change the shape of my comment. The backspace thing is a little thing, but it’s persistent and frequently annoying.

            Also *fewer :p

    • TWeaK@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      20 days ago

      Basically when you press backspace the underline for autocorrect extends over the space before the word, then when you press backspace again it deletes that space. Every other press of backspace will delete the space before, completely messing up the text when you’re just trying to make a minor correction. You then have the hassle of pixel hunting to get the cursor in the middle of the word where the space was to add it back again.

      • Hadriscus@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        20 days ago

        Ok my bad seems like I recalled incorrectly, your description fits exactly my experience. It’s the keyboard

        • TWeaK@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          20 days ago

          It’s not really the keyboard though, the keyboard works fine everywhere else. It’s a poor implementation from the text editor that Jerboa uses, one that other keyboards have created a workaround for. But the issue is in the text editor.

          It’s like when a website only works in Chrome, but doesn’t work in Firefox. It isn’t because Firefox is broken, it’s because the website doesn’t follow web standards and has only been tested in Chrome.

          • Hadriscus@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            20 days ago

            I see, there’s the keyboard on one side and the text editor on the other, and they don’t mesh well ? that makes more sense

  • Bo7a@lemmy.ca
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    21 days ago

    Sorry to fork the conversation, but I noticed nobody mentioned connect. Are these other apps really a lot better?.

  • Varyk@sh.itjust.works
    link
    fedilink
    arrow-up
    4
    ·
    21 days ago

    what phone do you have?

    use whatever app you want, I’m just curious because I’ve been using jerboa since the beginning without any issues, im on a pixel 6.

    did you try using a different keyboard?

    • TWeaK@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      21 days ago

      Part of the reason for the move is upgrading from a Poco F3 to a Pixel 7 Pro (although I’m sad to lose the IR blaster). However I run custom ROMs, so I’ve been using the keyboard that comes with DivestOS and AXP.OS. Don’t really want to try another keyboard lol but others have said that might fix it.

      • Varyk@sh.itjust.works
        link
        fedilink
        arrow-up
        4
        ·
        21 days ago

        got it.

        i hope the 7 is good, I’m donnne with pixels after this guy.

        i hear they’re great with custom roms but haven’t tried replacing mine yet.

        • TWeaK@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          21 days ago

          Yeah DivestOS ticks nearly all the boxes for me (eg call recording and custom gestures eg long press back to force close), however there were a few little niggles that custom ROMs have with other manufacturers - the camera is usually closed source so you can’t quite get all out of it, and also I was having issues with pocket detection where a message or call would turn my screen on and then it would either answer in my pocket or mess with the audio player on the lock screen. Not had any of those issues so far with the Pixel.

          However curved screens suck balls, and the cheap screen protector I got is already cracked lol.

          • Varyk@sh.itjust.works
            link
            fedilink
            arrow-up
            4
            ·
            edit-2
            21 days ago

            haha, dang. man the stock camera pixel 6 app is horseshit for me, even taking .raw photos it applies filters and effects that there’s no way to disable.

            over been wondering if camera apps are the alt option to go for, but i take videos much more often than I take photos anyway, so it isn’t too frustrating…except every single time I want to take a candid picture haha.

            yea curved screens can get outta here.

            have you tried grapheneos? everyone was encouraging me to try that on one of my pixel 6 rants some months ago.

            • TWeaK@lemm.eeOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              21 days ago

              I was tempted by GrapheneOS, my son used it for a while on his older Pixel, but I always resented all the diva drama from the devs. AXP.OS seemed like an easy transition, basically using the same ROM as my old phone (AXP.OS is a DivestOS fork).

              • Varyk@sh.itjust.works
                link
                fedilink
                arrow-up
                2
                ·
                21 days ago

                yea that one dev sounded like such a douche I stopped considering it, didn’t really want to be associated with the whole scene.

                well nice, enjoy and good luck on finding your next preferred client app.

  • edric@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    21 days ago

    I use Thunder on IOS, but since it’s cross-platform and assuming the experience is the same, I recommend Thunder.

  • Player2@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    21 days ago

    I tried the paid ones like Boost and Sync but eventually have settled on Thunder. It mostly just works and is still being actively developed

  • CrayonRosary@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    20 days ago

    Thunder is fantastic. It’s so good now. Lots of customizations, and it’s actively being developed.

    The markdown support is good, and spoiler tags are done right. It has it’s own YouTube video player now, too.

    The only issue I’ve found recently is superscripts rendering funny. Let me try one again.

    This number should be a superscript1 more words.

    Oh, it’s working now. The other day or at putting a line break before the superscript.

    • TWeaK@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      20 days ago

      Oh! Here’s the ultimate test: [1]

      Can it handle Markdown citations???

      Even the website doesn’t handle those quite right.

      The links should scroll between the citation in the text and the definition at the bottom, while I actually wrote the citation immediately afterwards. The website scrolling doesn’t quite work, but it does at least place the definitions all together at the bottom.[2]

      View the source for fun.

      Oh, maybe the website does handle it ok, it just doesn’t quite work on the first click. Subsequent clicks seem to scroll correctly.


      1. I wonder. ↩︎

      2. I’m kind of just extending this comment now to make it more likely to scroll correctly on a phone. ↩︎

      • CrayonRosary@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        20 days ago

        Neat!

        The content isn’t long enough to scroll, and the superscript doesn’t look like a link. Tapping it just collapses replies now that I’ve replied.

        Tapping the little arrow doesn’t collapse replies, so it’s doing something. It might scroll up if your comment were long enough.

        • TWeaK@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          20 days ago

          Good stuff hah. Thunder is in my trial group now anyway :)