I'm pretty sure abegee is referring to me, so I'll answer these questions.
Originally Posted by hrminer92
I've been fighting to get several serious issues addressed that are affecting webOS 2.x users and developers and have been getting nothing but the runaround. I've been in contact with many different HP dev relations folks and all of them tell me they're going to investigate and get back with me, and none of them ever do.
These issues include:
- Media permission bug that causes all 3rd party music apps to stop working: Have been dealing with this issue for almost 5 months and have had dozens and dozens of support emails from people asking me why my app (Music Player Remix) has stopped working. A couple months ago Ben from HP developed a "media permissions reset" app which I tested for him. He was supposed to release it into the catalog, but that still has not happened. A few weeks ago Gray Norton at HP said he'd be working to get the app submitted and would get back with me. I haven't heard from him since (after sending several follow-up emails).
- People running webOS 2.0.1 can no longer see my app (Music Player Remix) in the catalog. This includes people who paid for my app and potential customers (you know like all Verizon Pre 2 owners). HP has confirmed this is a bug, but almost 2 months later it still hasn't been fixed. In the meantime I've been getting tons of emails from existing customers and people wanting to buy my app asking me why they can't find it in the catalog.
- People running 2.1 on doctored devices can no longer see my app (Music Player Remix). This includes people who paid for my app and includes people running official 2.1 doctors (such as O2 customers). This issue affects all 2.x apps that have recently been updated. Again HP confirmed this was a bug a month ago but still hasn't fixed it.
- Download stats have been wrong for months. This affects all developers. Chuq just posted an update today saying it's still being worked on. In the meantime, developers have no guarantees that their download totals are accurate.
So it's not about HP dropping support for a dead framework (Mojo). I'm in complete support of them moving to Enyo. What I'm referring to is HP dropping support for users and developers of their current generation devices. All the issues listed above affect webOS 2.x users and developers who are entitled to receive support from HP.
This is why I've decided to hold off on working on an Enyo project, which would have been Music Player (Remix) for the TouchPad. I can't dedicate the amount of time necessary to convert Music Player (Remix) to Enyo when I see how HP is abandoning their current-gen users and developers. How do I know they'll support me and my users in the future when other issues arise? Once the TouchPad and webOS 3.0 is released, you think their next-gen development will stop there? The next big thing will be webOS 3.x on phones. After that, they'll work on webOS 4.0. And the cycle will continue.
P.S. In reference to the actual topic of this thread, an HP dev relations rep (Adam) contacted me asking me about Music Player (Remix) for the TouchPad and offered to send me a loaner device if I needed it. I told him I was going to be starting development soon (this was before my decision to halt Enyo development due to these issues). A few weeks later he emailed back asking for a status and I told him I was halting Enyo development because of these issues. He said he'd investigate them for me and get back with me...guess who I've never heard from since?