I won't have time to bring the app to release quality this year. But ignoring a "few shortcomings", the app is useable now.

If anyone have an unlocked phone, feel free to send me a PM and I'll send you the XAP file that can be deployed on the phone (I have only used the official developer unlocking, I have no idea if it works with the unofficial unlock).

It looks pretty much like the youtube video I posted earlier in this thread, except it now has page transitions, support boxsets, use a pivot control to determine sort order, and supports grouping (jump to alphabet letters, production year, or running time).

Known issues:
* When jumping to a group header (alphabet letter etc) or collapsing a boxset, thumbnails will not start loading before the list is scrolled slightly.
* Lifecycle management - the app doesn't behave as well as it should when you navigate back to it from another app.
* Profile panorama pages with no content are not hidden.

Things you would expect it to do that it doesn't:
* Display (and filter by) media type.
* Sort by purchase date.
* Display cover images full screen.
* Display movie details (no studios, rating, etc - it only displays covers, overview, cast, and crew).

Quoting Edelasos:

Quote:
And what say Invelos?

Nothing.

Quote:

There are plans for a version Windows Mobile 7?

Nothing has been announced. From a business point of view Android probably makes more sense, but then WP7 is way ahead when it comes to development environments, so maybe that will tempt Ken, we just have to wait and see. At least I have my collection on my WP7, so I'm good while I am waiting

Quote:

rather than the version for Windows Mobile 6.5 to Support should be more likely to develop a new version for Windows Mobile 7 or not?

It seems you are not realizing that it will be a LOT more work to make a WP7 version than it is to maintain the WM version already done. Of course if the work was the same, it would be best to go for WP7 - but the work is not the same.

Quote:

New devices with Windows Mobile 6.5, it will hardly be ...

Correct, but what has that to do with anything? Just because he stops maintaining WM6 doesn't mean he magically get's enough time to make Android, WP7, and whatnot.... specifically not when he is also spending time on things like Facebook integration that some people like.

PS: Please notice there is no such thing as "Windows Mobile 7". It's "Windows Phone 7".

Quoting skippyg3:

Quote:
... With the following that this product has I don't see why they wouldn't write their product for every platform.

I can think of a very simple reason: Time. A programmer can only spit out that much code a day, and that doesn't increase just because it makes sense to support a new platform.

MonoTouch/MonoDroid is addressing this, but realistically only the model and data connections can be shared between the platforms - the UI will still have to be built for each platform. And it's not yet completed for Andriod, and wasn't available when Ken started the iPhone project, so now he is stuck with non portable Objective C/C++ code.

Thought about it yes, but I am not going to make any commitments.

any new news on your app? I would really love to get it. accessing the website on a mobile web browser is a real pain lol

Yes, I'm also using it and it's great.
Shame that Invelos couldn't care less for us users of Windows Phone...