As an update after doing some digging the issue was raised with Google and acknowledged relating to Jetpack Compose:
https://issuetracker.google.com/issues/227625842
In the connected issues from that and connecting the dots they apparently fixed the problem with 1.3.0-alpha3 foundation unless I missed a dot.
Just an FYI GrapheneOS doesn't have its own Keyboard. The Keyboard that comes as default is the baseline AOSP Keyboatd. This seems like a very niche issue for it though, however personally I use Florisboard. Wh8ch is a candidate to replace the AOSP KB when it reaches a mature enough point and is feature complete.
Enjoying NOSTR and Amethyst, just want to let everyone know, I am here on an outreach basis to find people interested in or seeking information or support related to GrapheneOS.
Please feel free to reach out if I don't find you first.
Look forward to engaging with you all.
Not really, however durimg my brief time using Amethyst the main UX improvement would be being able, after doing a search, engaging with a result, to go back to the search results as opposed to the global feed and having to search again each time.
To address the main thrust of your question yes GrapheneOS shares parity or is better in comparison to iOS.
However based on your reference to the Android based alternatives you shoild keep the following in mind...
GrapheneOS and CalyxOS are much different. GrapheneOS is a hardened OS with substantial privacy and security improvements:
https://grapheneos.org/features
CalyxOS is not a hardened OS. It substantially reduces security. It recently went 2 months not shipping standard security patches.
Compatibility with Android apps on GrapheneOS is also much different. GrapheneOS provides our sandboxed Google Play compatibility layer:
https://grapheneos.org/usage#sandboxed-google-play
Can run the vast majority of Play Store apps on GrapheneOS, but not CalyxOS with the problematic microG approach.
CalyxOS is closer to LineageOS and they both always use multiple Google services too and give them privileged access even if users don't use microG. It would be wrong to imply they don't use Google services. microG is of course an implementation of Google services. GrapheneOS doesn't use Google services by default.
To clarify further they always use Google services even without microG. They use Google for connectivity checks, network time, attestation key provisioning, SUPL, DNS fallback (LineageOS only), PSDS (Pixel 6 and 7), eSIM activation and more enabled by default.
https://blog.privacyguides.org/2022/04/21/grapheneos-or-calyxos/ is a 3rd party article explaining some of the substantial differences between GrapheneOS and CalyxOS. It's a common misconception that they're similar. CalyxOS is far more similar to LineageOS than GrapheneOS. There are many other alternate OSes available.
https://privsec.dev/posts/android/choosing-your-android-based-operating-system/ is another article about privacy and security differences between alternative Android-based operating systems. Talks about other alternate operating systems including DivestOS. Unlike most content, these are based on real experience and technical details.
This would generally only be the case where both versions share the same package name and you have Amethyst installed in more than one user.
I am just getting my feet under the NOSTR table but so far Amethyst works fine on 0.25.1+