View Single Post
onethreealpha's Avatar
Posts: 434 | Thanked: 990 times | Joined on May 2010 @ Australia
#87
Originally Posted by Scorpius View Post
Exactly my thoughts. I don't want another dead-end phone.
This is an entirely reasonable perspective and yet also interesting given the fact that with the standard life cycle of modern smart phones frequently being tied to the duration of the contracts that they may be acquired on and the actual hardware itself (be it specs or capabilities), most people move on after 18-24 months.
Certainly after sales support and updates are important, but what benchmark should we apply to Jolla?
The same as Nokia with the N900 or N9 (the n9 in my opinion, despite the "wontfix"es recieved a good level of support and many more updates than most Android handsets), the same as most android OEM's?
In the app-centric marketplace that the mobile space has become, I will be interested to see how Jolla manage the development and expansion of native apps. Having a viable and functional Dalvik layer is all good as a stop gap, but can't guarantee 100% integration with the core OS and shouldn't be seen as a replacement for development.

BB have invested a fortune recruiting and assisting devs and it has worked, certainly with regarding to rapidly building the numbers in their app store. Jolla has neither the funds or capability to do this and will have to rely on piggybacking on to existing conferences and hacker activities.
With Qt Developer Days not until the last quarter of the year, I expect to see a high level of interest there, but little time
beyond that, before christmas to build and deploy through a QA process to an app store/market front before release.
they'll certainly need more applications to support launch that what they have HERE right now
__________________
Always remember you're unique, just like everyone else.
 

The Following User Says Thank You to onethreealpha For This Useful Post: