According to Fitt's Law - The time to acquire a target is a function of the distance to and size of the target.
I agree that I think distance between the menu and the bottom sheet is substantial.
This solution allows placing a lot options in one place.
No you don't missing something - it's a good practise.
The other solution in this circumstances is ...
What you already have is good. Listing a few things that may help improve –
Align text to left, so that both text and buttons are aligned.
Increase whitespace around the content to make it look more centered.
Use text-link for the secondary CTA. This will improve focus on the primary and maintain content alignment.
I think it is based on the user expectations and as a user, I don't expect to see the "Home" button in the top-left of the screen in a mobile application
Expectations with the home button in an app
When I see just a Home icon, I would be hesitant to click it because I can't be sure of how to get back to the previous screen. Also, I might not be aware of ...
Try testing the smallest effective difference with your users.
If some of the rows are offering details on touch, you can test with your users if a link color works. Since the whole row is tappable, You could try making each value per row as a link.
You could try a background color if need be as well. This might run the risk of being confused with a ...
Unless the users are aware of this setting in your app, it will be difficult to get them to use it. Instead of putting it inside Preferences, if it is really important, it could be separated into its own option to stand out and be easily discoverable.
It is important to ask what advantages does it offer to the users in doing it this way. Does it offer them ...
At times a lot of these can be classified as anti-patterns since the guidelines for how Bottom Sheets should appear are very vague. The purpose of a bottom sheet is to appear to be easy to reach for the thumb or index finger while providing an alternative to a popup or similar content accessible for taller displays and one handed use.
Essentially I believe ...
I find it is best to include the UI back button by default (for the reasons listed by @Tin Man as well as parity and operational efficiency when designing an app for both iOS & Android). However, you should consider the implications of doing so on a screen-by-screen basis.
Additionally, you may want to specify different actions for the hardware back ...