Where do you suggest we should place it?

It should still be there, can you go in the settings disable the show navigation bar setting, and check if it now appears? If so then it hidden behind the navigation bar. Which should be fixed in the next release

The biggest performance changes should be from 0.0.56

Due to a compound of factors:

• Upgrade of Jetpack Compose, the toolkit we use for the app, they have done some optimizations
• Stability config change (Basically we tell Compose these elements are stable)
• More memozation of function calls

Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, "keep the same UI element as before", it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second

In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)

Google does some amazing work, it just takes them a long time. Once this patch lands we should see more optimizations https://issuetracker.google.com/issues/241154852

I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i'll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.

Jerboa uses Jetpack Compose as toolkit instead traditional Views system that most apps use. The problem lays at core of a textfield component. It affects every app that uses this toolkit. And we can't fix because it would need to be fixed at very low level, we don't have access to nor domain knowledge about.

What crashes do you experience? Could you go to settings > About > Crash logs and sent the recents ones to me

This is already fixed, it ships with 0.0.48

We cannot solve that issue on our end. It is a problem with the toolkit that we use, see https://issuetracker.google.com/issues/294102838

There is a mark read on scroll option, that marks every post read that you scroll past

Jerboa will support it once there is support for it in the API, This support will most likely come with 0.19 see https://github.com/LemmyNet/lemmy/pull/3869

Jerboa uses Jetpack Compose toolkit, instead of traditional Views approach. It is not mature yet and the source of many of these problems you are experiencing. It works well with Gboard but not so much with other keyboards.

• Weird behaviour on text removal on OASP keyboards or derivatives https://issuetracker.google.com/issues/294102838 https://issuetracker.google.com/issues/221636606
• Or this one where when you are typing your text starts getting behind your keyboard https://issuetracker.google.com/issues/266094055
• Or this which causes stuttering behaviour in some scrollable contents https://issuetracker.google.com/issues/250632404

There is a loadingbar below the search that loads when it is searching

Make GitHub issue with full logs