Privacy Browser Android

V X wrote:

Being able to set PB as the default Assist and Voice Input app.

This would allow for the browser to be opened by holding the home button thus making it more easy to access the browser and also serve as the default search app.

That is a good idea. I would be willing to do so as long as it didn't involve any additional permissions. I have created a feature request at https://redmine.stoutner.com/issues/611.

A tab list drawer/panel accessible by sliding-down from the URL-bar With option to export as text all selected/opened-tabs.
PB is not meant to support sync but for those times when one has been doing some research and would like to export/save those URL for later use locally or to be shared via the share menu.
- I can see this working with bookmarks as well. A way to bookmark more than one tab at a time under a folder or tag.
- Also, the visual gain of an unobtrusive easy to access and exit list of all opened tabs

I'm not sure the sliding menu would work well, especially with the possibility of having the app bar optionally move to the bottom of the screen. https://redmine.stoutner.com/issues/143

However, I am open to the idea of having a bookmark all button. I have created a feature request for that at https://redmine.stoutner.com/issues/612.

Also, there is some consideration of creating an automated import/export that could include current tabs. https://redmine.stoutner.com/issues/318

In addition, there is an existing request to create a secondary tab interface similar to what you have proposed. https://redmine.stoutner.com/issues/525

Soren Stoutner wrote:

V X wrote:

Being able to set PB as the default Assist and Voice Input app.

This would allow for the browser to be opened by holding the home button thus making it more easy to access the browser and also serve as the default search app.

That is a good idea. I would be willing to do so as long as it didn't involve any additional permissions. I have created a feature request at https://redmine.stoutner.com/issues/611.

- I don't know how to reply directly on the feature request ticket.

I hope there isn't any extra permission needed for this feature. If this feature can be implemented, do consider adding the option to have a new tab open every time one opens PB via holding the home button down.

A tab list drawer/panel accessible by sliding-down from the URL-bar With option to export as text all selected/opened-tabs.
PB is not meant to support sync but for those times when one has been doing some research and would like to export/save those URL for later use locally or to be shared via the share menu.
- I can see this working with bookmarks as well. A way to bookmark more than one tab at a time under a folder or tag.
- Also, the visual gain of an unobtrusive easy to access and exit list of all opened tabs

I'm not sure the sliding menu would work well, especially with the possibility of having the app bar optionally move to the bottom of the screen. https://redmine.stoutner.com/issues/143

I'm not an app developer but if the argument is aesthetics then I don't see an issue. In the came the App-bar can be moved to the bottom of the screen then the sliding up panel should work well as a mirror of top.

See attached image.

However, I am open to the idea of having a bookmark all button. I have created a feature request for that at https://redmine.stoutner.com/issues/612.

Also, there is some consideration of creating an automated import/export that could include current tabs. https://redmine.stoutner.com/issues/318

In addition, there is an existing request to create a secondary tab interface similar to what you have proposed. https://redmine.stoutner.com/issues/525

V X wrote:

- I don't know how to reply directly on the feature request ticket.

Click on the edit button on the right of the screen under the last comment.

I'm not an app developer but if the argument is aesthetics then I don't see an issue. In the came the App-bar can be moved to the bottom of the screen then the sliding up panel should work well as a mirror of top.

The problem isn't an aesthetic one. Rather, on newer versions of Android, the swipe up from the bottom of the screen gesture is already taken by the OS. Unlike the swipe down gesture from the top, which starts above the screen, the swipe up gesture from the bottom starts on the bar at the bottom of the screen--much narrower when the gesture interface is enabled--that is only pixels away from where the App Bar would be placed. I can foresee this causing a lot of user frustration. You never want your interface to accidentally do something different than what the user thinks they have told it to do.

See attached image.

Thanks for the mockups. If you are not familiar with Android's new gesture interface, you can get some sense of how skinny the navigation bar is in the screenshots at https://www.stoutner.com/privacy-browser-3-5/.

Soren Stoutner wrote:

V X wrote:

- I don't know how to reply directly on the feature request ticket.

Click on the edit button on the right of the screen under the last comment.

Thanks

I'm not an app developer but if the argument is aesthetics then I don't see an issue. In the came the App-bar can be moved to the bottom of the screen then the sliding up panel should work well as a mirror of top.

The problem isn't an aesthetic one. Rather, on newer versions of Android, the swipe up from the bottom of the screen gesture is already taken by the OS. Unlike the swipe down gesture from the top, which starts above the screen, the swipe up gesture from the bottom starts on the bar at the bottom of the screen--much narrower when the gesture interface is enabled--that is only pixels away from where the App Bar would be placed. I can foresee this causing a lot of user frustration. You never want your interface to accidentally do something different than what the user thinks they have told it to do.

What about having the gesture be on the tab-bar itself.
Slide down/up from the tab-bar. The gesture could also be something like "touch hold on tab-bar & slide down/up.

When the app bar is at the bottom, presuming the tab-bar would be top-most thus placing it further away from the bottom edge of the screen. Once the user know where to start the proper gesture for the tab-list to be summoned, with a little bit of practice the placement and gesture should be second-nature.

See attached image.

Thanks for the mockups. If you are not familiar with Android's new gesture interface, you can get some sense of how skinny the navigation bar is in the screenshots at https://www.stoutner.com/privacy-browser-3-5/.

V X wrote:

What about having the gesture be on the tab-bar itself.
Slide down/up from the tab-bar. The gesture could also be something like "touch hold on tab-bar & slide down/up.

When the app bar is at the bottom, presuming the tab-bar would be top-most thus placing it further away from the bottom edge of the screen. Once the user know where to start the proper gesture for the tab-list to be summoned, with a little bit of practice the placement and gesture should be second-nature.

Possibly, but I would prefer to do something that isn't so convoluted.

I must say that I like the linear layout of your mockup much better than most of the tab interfaces on other Android browsers. When I get around to implementing this feature I will probably go with a design similar to your picture.