You are both right. The functionality gap is widening and Jolla dvelopers have a lot on their plate.

When reading your posts, the two highlighted bits stood up at me like sore thumbs. I do not know anything about Jolla's internal processes but I can tell you this from my own experience. I have worked in a wide range of environments, under a wide range of management and using a wide range of methodologies and development processes. And the things I always found the most demotivational could be summed up in just two bullet points:

• A lack of clear direction. The management may have an idea where the project is going but this is not being communicated to us little pawns. This leads to micromanagement: they tell you to do X, without telling you how it fits in the big picture or even who works on Y that directly interacts with your X. The impression is that even the management has no idea where they are going.
• An ever-growing backlog. You know there are 125 issues on the list, some of them serious and some of them with thousands of users crying for months if not years. Yet your manager asks you to work on a new feature that no one has ever asked for and while you are working on it, the backlog grows from 125 to 132.

Maybe it's just me but I found the two extremely demotivational and leading to running around in circles, with the result that you are constantly overworked and yet, when you look behind, you do not see any results.

I found this at work as well as in private life. There is no point opening a savings account while you have outstanding debts. Pay off your debts first otherwise they will continue increasing. Equally there is no point starting a new thing when you have 10 things unfinished. You will end up with 11 things unfinished.