User feedback

[huyphams]

1. Which driver are you using and version of it (Ex: PostgreSQL 10.0):

2. Which TablePlus build number are you using (the number on the welcome screen, Ex: build 81): 152

3. The steps to reproduce this issue:

Noted: If the bug is related to data, please attach an example SQL data.

Moved from https://github.com/TablePlus/TablePlus/issues/2264

I hate how table plus makes tabs, they disrupt my workflow.

I came over from using Sequel Pro, which as become buggy and unusable over the last few years, not because it isn't well thought out but because it crashes and acts oddly quite frequently these days. Also, I've taken to using windows and Sequel Pro will never be anything other than a Mac program.

Sequel Pro has a similar interface to table plus, but does not automatically open tabs, but I've never felt the need to open a tab while using it. Now that I'm using Table plus, I find the automatic tabs annoying and disruptive. I've also noticed that you've hinged your whole paid model on tabs.

My issue with tabs: normally when I use an app that has tabs, I have to click a plus or do something explicit to create one. Therefore I make a conscious decision to make a tab and I've already created the brain space for that tab. Table plus opens tabs on it's own implicitly at times that don't make sense to me. If I purchased table plus I imagine opening 100 tabs over the course of the my day while ignoring all of them and then periodically closing all but the current one. The current warning at 3 tabs is nice because it prevents me from doing this. This creates a disincentive for me to buy table plus because buying it will make my experience worse. As a software developer I appreciate the software you've created and I don't want to remain in the free tier,

What to do instead? just have one workspace. and any act that currently opens a new tab should just change the current workspace. The only exception to this would be the the SQL Editor, which in my mind doesn't feel like it should open a tab regardless, cause it's completely different from everything else and tabs generally imply the idea of threading a common task. There should be one SQL editor, and so long as it retains whatever I last typed into it when I click on it I'm good.

I know that I'm probably not jiving with the design philosophy that you all are aiming at, and that you probably think I'm wrong, but I can't be the only person who uses table plus this way. I appreciate good software and this is good software, that I would like to pay for, but I'm currently in a situation where if I pay for it, my experience with it will get worse. maybe you should switch to some other mechanic like a query limit or something else to trigger the trial limit, forcing the user to restart the program when they bump up against it, I don't know just a thought. I really think the current user experience surrounding tabs makes no sense though.

[jonatandorozco]

@huyphams Taking in account your recommendation I moved the issue to this one

I consider we'll have a better user experience if we make some changes to the way tabs are opened

For somebody that uses many tables temporally will open many tabs and we have to close those tabs to keep everything organized.

1. Overriding the current active tab if I press click on a table and the current tab is not an SQL query
2. Pressing double click into a table will open a new tab