You are viewing a single comment's thread from:

RE: Re-Discovering The Hive Keychain App For Mobile (A Must-Have App)

in LeoFinance • 3 years ago

Thanks for the review! =)
Can I ask which device you are using, I see there is only one column of tabs in your in App browser when there should be actually two, I want to test this out

3 years ago in LeoFinance by
$0.00
    Reply 2
    Sort:  
  • Trending
    • [-]
     3 years ago  

    Thank you!

    I am using Huwaei Nova 3.

    It's my second day using the app browser, mainly peakd. Here are some i noticed:

    • The browser back button does not work. So if say for example I clicked a post on my feed and am done reading, back button wont take me back to my feed. I have to click the peakd icon at the top left again. Of course that takes me back to the top most post again instead of from where I left off.
    • there's no refresh button (pull down to refresh)
    • sometimes the keyboard covers the preview when typing, like this one.
      Screenshot_20210914_101155_com.mobilekeychain.jpg

    I presume you are still working on a lot of features here. So far there are ways that i can work around with the above observation. Looking forward to more developments and thanks again for creating this app.

    $0.00
      Reply
      [-]
       3 years ago  

      The browser back button does not work. So if say for example I clicked a post on my feed and am done reading, back button wont take me back to my feed. I have to click the peakd icon at the top left again. Of course that takes me back to the top most post again instead of from where I left off.

      I ll look into the back button but it's supposed to be directly implemented in the webview. I guess its due to the fact that peakd doesn't actually change page when you navigate, it rewrites the url instead, I'll look into it.

      For the second point, I didn't put the pull down to refresh yet, but there's a button for refreshing the page in the middle of the bottom bar.

      For the third point, I don't think there's a way around this, mobile devices handle inputs that way by default, opening the keyboard just underneath the active input. Even if something can be done, it would be on peakd side, since we cannot handle display of every dApp on our side case by case.

      If you have any remarks or request features, don't hesitate to drop them on our Discord or Github =)

      $0.00
        Reply