4 ms·
I checked out Baqend ("we" in the article) and the site prevents me from navigating back when I press "back" (I think by injecting itself as the previous page -
by crdb 10y ago
I checked out Baqend ("we" in the article) and the site prevents me from navigating back when I press "back" (I think by injecting itself as the previous page - I'm not really up to date on dark patterns).
This is the kind of behaviour that is an auto-no for me when buying B2B, not just by itself but because of what it signals about the company. I recommend you remove it.
On the article itself: you can do very fast pages off a relational DB. In one case, the round trip on a Postgres full text search for auto complete on millions of rows from multiple tables was so fast we had to add a 10ms delay - on a $5/month VM.
- daveguy 10y agoIt looks like the dark pattern they used to get that "no back" behavior is: "open in a new tab". Edit: I stand corrected, link from the article opens in a new tab, so the back issue is moot there. Definitely red flag behavior. Baqend folks, if you are listening, you should fix it, and if it is the default behavior of your framework you should definitely fix it. No one likes hijacked back buttons.
- crdb 10y agoHow to replicate: google "Baqend", click on their page (should be top result), press back button, press "back" arrow on browser. Screenshot: http://imgur.com/a/mLXdc http://imgur.com/a/mLXdc Compare with: http://imgur.com/a/UnQOG http://imgur.com/a/UnQOG
- DivineTraube 10y agoThanks a lot, it's fixed now.
- erikwitt 10y agoThat is definitely unintended behavior. We'll fix it! Fortunately, only www.baqend.com has this bug, it's not in our framework.
- DivineTraube 10y agoWe fixed that problem and deployed it. It turned out to be the iframe with the tutorial app. That sets a new hash with a random todo list id and that captures the back button. It was not intended to keep people on our site. Thanks for pointing the issue out! BTW, I agree, RDBMSs are a great choice if the hot data set fits in main memory and queries are well-optimized through appropriate indexes. Issues usually only start to occur if 1) the data set is too large 2) queries cannot be optimized by the query optimizer and involve full-table scans 3) interleaved transactions contend on few rows.
- pjc50 10y agoPeople often point out web design flaws in pages submitted to HN, but so rarely do we see an author come back, accept the criticism, fix the problem, and report back. Thankyou!