scorlibrian
New Head-Fier
No. At least I'm not. I'm unhappy with my decision to purchase the EM5 and I've been very vocal about that earlier in this thread.Are we normalizing paying 1000$ for products put on the market unfinished (abandonned) because features are not easy to implements?
I'm a project director in mobile dev, half the work is the CI and QA. What we're seeing here is something that need to be called out.
To clarify, I don't think there's anything wrong with calling out something that's wrong with the software. I encourage it. It's the only way to make sure our voice is heard.
However, there are different levels to this.
- Features that are broken. These are features that are in the software that aren't working as intended. These are things that absolutely should be fixed and should be of the highest priority.
- Features that we expect. These are features that are the bare minimum of what we expect from the software. Otherwise, the software wouldn't function properly or as advertised. These are also things that should be relatively high on the priority list of what should be worked on.
- Features that we want. There's a really blurry line between the last category and this one, and a lot of people confuse features that we want with features that we expect. These are features that Shanling hasn't made any claims about for their product and we've only requested the features because we see value in them. I still think it's good to request these features, but I wouldn't expect Shanling to prioritize them. And it's unfair to call a product "unfinished" because these features aren't implemented.
So what am I doing about it? Well, there's not much I can do. I can continue to post feature requests about it on the internet if I want, but that's been a waste of time so far. I'll tell you what I'm NOT doing though. I'm not buying another Shanling product again. Sound is great, but the lack of software support is a real dealbreaker for me and I feel like I could cobble together a better system out of multiple components driven by a raspberry pi rather than buy another AIO and be beholden to their software team.
However, the discussion in this thread was moving away from "this product is bad" or "this product doesn't do what I want" and moving towards "The Shanling community rep should force the devs to work on the feature I want" and "the Shanling software devs are lazy/inept/stupid", and I wanted to move away from that.