karimmaassen

Simplicity is not about making complex things simple, it's about making it simple to do complex things.

I'm a BIG fan of my 13 mini. Bought it last December and absolutely love the small form factor. The battery is no problem at all, even with extensive use. I easily have 20% or more left at the end of the day and it's not even an issue when having it used for CarPlay.

I'm saddened by the idea there will never be a mini again.

Safari user here. I often feel I'm a minority, but it's a really good browser for my Mac. Had been using Firefox after Chrome before switching to Safari.

What I find the real problem is not JIRA itself, but the fact that most of the time JIRA, is abused up to a point where it's become unusable. The inability or unwillingness (or both?) of the teams I've worked with to structure their work, write good user stories and keep things simple is in my experience the root cause of any shitty JIRA experience I've had. Of course it doesn't help per se that JIRA allows you to do that, but I guess that's not the tool's fault. (You can write bad and good essays with Microsoft Word).

For the Dutch speaking community, Orkut has always had a strange connotation to it, as part of the name is a swear word.

Here's the thing: Finding a solution to a problem, then making it into a business that is sustainable (read: had money influx) during dire times (read: economic recession), is a very good and healthy beginning for your start-up.

Doing startups when money is sloshing around, often leads to zombie companies that are on life support.

The panic in startupland stems from the fact that most of them are cut off from said life support.

Honest question: does any of you use Firebase and why (not)?

It's never lupus

But you would not be destroying data. It's an UI interaction which you're applying (i.e. closing the modal view, and thus navigating back to the previous state of your UI).

I agree with you that modals are abused. Modals should - in my opinion - be used for immediate actions such as your example.

Side panels however are fine in my book. In the end, we're talking about the same thing: example.com/fruits/new - Navigating (there you have it) to this URL should provide the user with an interface to fill out a form to create a new fruit.

In practice this could just as easily be a side panel triggered from the fruits list page, by clicking on the "new fruit" link. The URL should reflect that UI state change.

Which one is UX best practice and why? A small exploration as to why one is preferred over the other.