Blog

Hey.com: Feedback on why I’m not going ahead with it

Two weeks ago I managed to receive an invite to the new email service Hey.com from Basecamp. I heard Kara Swisher interview Jason Fried about the service and was excited to give it a try.

I knew a full switch to Hey was not likely, even in the next 12 months, but I am a huge user of email subscriptions for news and updates and wanted to see if I could separate all those emails into a different service to start.

Alas, after 7 days I realised Hey is not yet for me. The UX (user experience) just isn’t there yet.

To be clear, I have purchased my first year subscription, primarily to secure the email address for the future. But I have undone all my email subscription changes.

I’m still 100% behind Hey and Basecamp in this venture. I think email needs a revamp and recognise Hey is still very early days. I have also provided feedback to Hey support as to my issues with the service at this time and wanted to that message here, in its entirety.

 

5 July 2020 8:40am

Hello,

I wanted to provide some feedback.

I was excited to join Hey, however, now that my 2 week trial is almost over I have decided not to continue with the service, and I wanted to provide some feedback on what predominantly does not work for me.

That being said, I have just paid my first year in order to ensure I retain the email address (for security reasons).

Ultimately it comes down to UX.

Hey’s UX is too divergent from what I’m used to with email. And while it certainly has some interesting ideas I hope to see succeed, my 25+ years of using email is a large weight of experience to compete against.

To be clear, I recognise my UX issues are very “personal” to me and how I work, and not necessarily work how your majority customer base works.
I also understand that Hey is “wildly opinionated”, but for me it’s a little too opinionated for the most important service I use.

(NB: I am also a software developer with an interest in software design/UX)

Specifically, the things that work against me are.

* “Imbox”. I don’t know what it is but I find that word really annoying.
I know the meaning of the word but every time I see it, it feels “wrong”.
Perhaps it’s my dyslexia or just a peculiar mind, but my brain struggles against the word and tries to convert it to “Inbox”.
Also, it is so a prominent as a title on the page. All the major page titles feel so unnecessarily BIG on the page (high visual weight) and compete for my attention all the time.

* I live through in my emails. I read, sort, organise and categorise.
major element I use is labels/folders. And I switch through them regularly. Having access to labels through a hidden menu (click 1), then a separate page listing them (click 2) is frustrating. Basically labels in Hey are useless for me because it’s too much work to get to them.

* Having the Imbox auto-sort in “last accessed” order is disorienting. I expect to see emails in reverse chronological order by default. Sorting by last accessed is a great idea, but not by default.

* I’d like the option to switch between my sort orders, including dates, titles and sender.

* I use stars/flags a lot in visually tag and group emails and that’s sorely missed with Hey.

* Seeing sent messages mixed with received messages in the Imbox/Previously Seen list  is strange and too much clutter. I need to see my sent messages <1% of the time and I’m happy to access them via a “thread” view or separate “Sent” list. They don’t need to be in my face

* The visual weight of the colour profile circle in the message list is just too much. Same for the “Hey” menu and my own profile menu.
When I scan the page my eye goes to the most prominent feature on the page, which at the moment is the profile icon.
I want my eye to be focused on the message titles, which it probably about the 3rd highest weight on the page.
In fact, when I analyse the page there is a lot going on in the page in terms of different colours, lines and shading.
To be honest, this really feels software designed by a software developer, not a UX or UI designer (i.e. something I would design myself).

* The “previously seen” list on the “Imbox” page drives me nuts! I strive for zero inbox, so seeing that list every time I enter the page makes me immediately think I have messages to action. When I finish reading a message I want to label it and archive it from view.

* And I really don’t want my read/unread message to slip between 2 lists on the one page. It breaks my expectation of where a message should be, partly because I’ll often read a message, drop back to my inbox, then later go back and re-read or mark it as unread. But now I have to find it in a different location (and probably a different sort order).

* The Feed… is too much like a social media news feed for me.
Separating subscriptions is the primary reason for me to trial Hey (at it’s an awesome idea) but at the moment it’s a fail, unfortunately.
I just need another area similar to Imbox but dedicated to my subscriptions.
I have at any one time 30+ daily subscriptions (this is how I receive most of my news and updates).
I don’t read them in sequential order, and some subscriptions I’ll skip reading until the end of the week.
I also hate social media feeds – there’s something about their nature and scrolling that my brain and eyes can’t handle.
So, it’s a real bother to have a list of partially open messages in my Feed (that I still always have to fully open anyway – which makes a partial view useless…?) It’s too much information. I just need to see the subject and who it’s from.
Or an option to switch between the “normal” Imbox style list and seeing the open message view.
A huge issue is I can’t tell when a message is “read” vs “unread”. And I can’t archive a message (hide it from view).

* When I move a message back to Imbox, future messages from the sender still go to The Feed, but I would expect them to come to the Imbox.

* It would be nice to have an indicator on the Imbox screen of how many unread messages there are in the feed. When I check Imbox I then need to manually check The Feed as well to even know if there are new messages (which I can’t really tell anyway because everything looks new).

* I was confused about where to find my “Drafts”. I intuitively looked under my “Hey” menu but couldn’t find it. Instead, it was under my profile menu, which doesn’t really make sense.

* I tried the “Set Aside” feature with some subscription messages, which gives me yet another page with yet another layout. What’s up with the tile view?
Then when I select “Done” it puts the message back in the Imbox “Previously seen” list, which is strange.
But I’m not even sure what the purpose of Set Aside is (didn’t read the help. Maybe it’s just me not understanding).

* I tried the “Reply Later” (which, for some reason, I expected the option to be able to set a reminder) and it put a sticky version of the message at the bottom of the Imbox. Which seems strange that I want to basically push something out of view for later but then you keep it displayed in my face?
I also can’t move a message from Reply Later back to Imbox.

* There’s no contextual feature help. All I can do is send a help message.
Why can’t I quickly look up info about a feature?
For example, I’m too afraid to try the “Merge” feature because I don’t know what it is. This is the one time I’ll use a help page, but I don’t know how to get to it.

* The “Hey” menu.
It’s too slow. That slight lag when opening the menu (browser, Windows app) get’s really annoying when you do it regularly and is very noticeable when I’m having to continually open it to jump between screens. And that “thunk” (“pop” or whatever you want to call it) when it finishes opening is disconcerting.
A smooth and instant transition would be nice.
Also, options to move between Imbox, The Feed, Labels (including the label list) that are always visible would be a welcome feature. That would cut down a lot of clicks through the menu every day.

* I’m a bit concerned about this: “at the end of your trial your account will be automatically closed, and all your data will be deleted from our servers 30 days later. Then your email address will be released back into the pool so someone else can sign up and use it.”
My concern is security related. If someone tries the service with and uses it for “sensitive” subscriptions or communications, then cancels but their address continues to receive sensitive info, then if it’s claimed by another person in the future will the originally person’s subscriptions come to the new person after they claim it?
As it is I’m now going to purchase a year’s subscription to secure my address and ensure no one else can access my trialled subscriptions.

* Not an issue but something to consider: I use multiple domains for my emails. And I use a different “username@” for each subscription and service I sign up for to identify when my email is shared, and as a layer of protection in data breaches. I know domains is something that’s coming but it’s a bit of a show stopper for me at the moment.

If any of these issues are actually features available, then you should know I didn’t look up any help and will not look up help. If I can’t discovered it via the UI or context help then, again, it’s a UX fail.

As clean and “focused” as the UI is, I think you need to realise that email is still a central tool for some people – particularly “older” (almost 40) people like me. I don’t been business/corporate either.
Email isn’t just about an inbox and “read once” message. It’s also about organisation and quick access. Re-imaging email is a good idea, but breaking the UX and features people have become used to is perhaps not going to win people over.

On a positive note, the things I do love are:

* Protecting against trackers. This is the key element that drew me to Hey when I heard about it.

* Having a separate Feed for newsletters, even though I have UX issues with it. I subscribe to quite a few a newsletters and wanted to separate them from my normal Inbox. I’m happy to pay just to have a separate inbox for these.

* No push notifications. That’s possibly going to be a problem for some people, but I’m really appreciative of it.

I’m still keen to see Hey succeed and wish you all the best, but unfortunately the service is not yet there for my own needs.

Cheers,
Jason

Sol Republic Shadow Wireless Headphones. Absolute Shit!

I’ve been using Sol Republic Shadow Wireless headphones for two and a half years now.

When I started with them they were great. Good battery life. Good sound. Good microphone. Rugged.

Now…

The microphone is shit – people tell me I sound like I’m talking through a long tube or I’m under water. And the earphones keep dying.

I’m on my 6th set and after just 2 months this one is fucked as well. My right earphone just stopped.

I buy my headphones from JB Hi-Fi and they come with a warranty. I even get the extended warranty. Which is a waste of money really because no set has survived the standard warranty yet.

So I’m going to get my replacement under warranty and that’s it. When the next one dies or I run out of warranty I’m changing brands.

It’s a shame because originally the Shadow was the perfect headphone for me. But given how much I use them reliability is more important than brand loyalty.

Sample of Static Header, Static Sidebar, Scrolling Content (CSS)

I’m working on what seems like a basic web layout: a static page header (stays in place when scrolling), static side menu (also stays in place) and the main column of content scrolls.

There’s a Codepen below that is “in progress” and shows it working. Bear in mind it’s not responsible yet – you need a screen >1024px wide. I’ll keep working on it to create a responsive option, so check back soon.

Something I want to point out is CSS frameworks can help with this situation. And they can hinder. I’ve taken to using the Bulma utility CSS framework lately and it’s great. But using its built in container/grid system I think (TBC) seems to be working against me. I also find myself needing to override the resets to un-reset certain typography decisions.

Sometimes it’s better to just do it yourself.

View the source code at https://codepen.io/jsnelders/pen/WNQrRbo.

See the Pen
Static Header, Static Sidebar, Scrolling Content
by Jason (@jsnelders)
on CodePen.

When people you respect start acting like dicks

There’s someone in my professional community I’ve listened to and respected for many years now.

I’ve consumed almost all their content. I listen to everything they have to say. I’ve engaged with them online. And I’ve even spent money on them.

But lately I’ve noticed a creeping from the shadows: they’re starting to act like a bit of a dick.

I’ve notice a bit of… how do I describe it – I think arrogance and hypocrisy are the words I’m looking for.

It’s nothing overt. More in they way they speak. What was once a consistent positive attitude and refusal to engage (at least publicly) with negative behaviour is now starting to turn. Where, on one topic they tell people “if you don’t like it, just ignore it”, on another topic they’re engaging in a fight they should just ignore.

While it’s not intolerable, it is a turnoff. To the point where every time I’ve wanted to engage with them online over the last few weeks I’ve decided against it, because I’m envisaging a hard-stop negative response from them rather than opportunity for a discussion.

And this is not good for the person, because they are their brand. They earn their living because of who they are – co ntinua leading authority in their domain.

And while they continue to be an authority, if long-time loyal “fans” (see Kevin Kelly) like me start turning away (perhaps even becoming vocal about their disappointment and affecting future listeners) then the authority will dilute their brand by turning away the people who matter most.

Sure, they won’t go out of business. But what was once the equivalent of Nike with a strong ambassador like Michael Jordan will become just another mall shoe store, selling a utility we all need but having none of the passionate following of something special.

I continue to listen to this authority figure. For now. But with me their reputation is already diminished. And if their attitude continues to aggravate me I have no problems tuning them out of my life (has they have themselves advised in the past). Life is too short for aggravation and there’s always someone else I can turn to for advice.

A better way to describe “on the bench” and “non-productive”

I just heard my wife, a corporate accountant, on a call with her team talking about people in the construction company she works for charging time to projects when they are non-productive (during this time of COVID-19 and working from home).

This is a similar situation to working in IT corporate consulting, where the consultants generally describe time back in head office between client projects as being on the bench. It’s a strange situation to be in – no fault of the employee but it holds a burden and shame many carry internally.

The great thing I heard my wife say was:

Let’s not use the word “non-productive”. Let’s use the word “non-recoverable“.

The words “on the bench” and “non productive” carry a negative connotation and place the focus (blame?) on the employee.

“Non-recoverable” or “non chargeable” on the other hand describe the situation just a well, better reflect it in business terms, and remove the negative inference on the employee.

It’s not like employees are ever without work to do (or things to learn).
The only difference between types of work is whether or not the business is directly charging a client for that slice of time.

[Vue warn]: Error in nextTick: “NotFoundError: Failed to execute ‘insertBefore’ on ‘Node’: The node before which the new node is to be inserted is not a child of this node.

I just had to deal with the following Vue generated warning:

[Vue warn]: Error in nextTick: “NotFoundError: Failed to execute ‘insertBefore’ on ‘Node’: The node before which the new node is to be inserted is not a child of this node.”

DOMException: Failed to execute ‘insertBefore’ on ‘Node’: The node before which the new node is to be inserted is not a child of this node.

It related to the following line of code, where I was conditionally displaying a Font Awesome icon:

<i class="fas fa-spinner fa-spin" v-if="bookmarkMetaState == 'retrieving'"></i>

The problem, I believe, is the original <i> element ended up rendering as an <svg> element. So the error makes sense, because the the original code no longer existed.

I simply wrapped my my <i> Front Awesome icon in a <span>, and applied the v-if to the <span>. Problem solved.

 

 

 

Is data returned by JavaScript (ES6) array.filter() immutable?

Is data returned by JavaScript (ES6) array.filter() immutable? It depends.

If the original array contains “primitive” values (eg. strings, numbers and boolean) then a new array with “copies” of the values is returned in the filtered array. Changing data in the returned array will not affect the original array or its data.

If the original array contains objects then the a new array is still returned from .filter() but each element still references the object in the original array. Changing data in either the original or returned array will affect the data in both array because it’s the same piece of data being referenced by both arrays.

 

I have a Pen at https://codepen.io/jsnelders/pen/jOPeXXw demonstrating both situations.

 

See the Pen
Is data returned by JavaScript (ES6) array.filter() immutable?
by Jason (@jsnelders)
on CodePen.

Use `//@ts-check` in Visual Studio Code to Find Undeclared Variables (and save yourself hours of hunting)

Oh. My. God!

I just discovered //@ts-check in Visual Studio Code.

For all the web/JavaScript developers out there, add that comment to the top of your .js file in Visual Studio Code (that’s all you have to do).

Now, any issues in you variables (like using variables you haven’t declared) will show as an error in the IDE.

This is what I call super charging your IDE and your development.

I could have saved myself half a day’s work yesterday if I’d thought to search for “visual studio code undeclared javascript variables” beforehand. 🤦‍♂️

See: https://code.visualstudio.com/docs/nodejs/working-with-javascript#_type-checking-javascript