Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (3)
to General by Kalatti - 2 days ago - more...
|
2010-12-07
, 18:50
|
|
Posts: 37 |
Thanked: 17 times |
Joined on Sep 2010
@ Karachi
|
#862
|
Hey peter,
From what ive gathered on these past few pages of posts, i understand the descision to put this Instinctiv for maemo on hold is difficult but at the same time inevitable and understandable. Between being dissuaded from the present (maemo5) and being uncertain about the future (meego), it makes perfect business sense not to invest more time and money into this.
If you can, release the update you and your team have worked on for so long, with as much as you can implement (perhaps the new UI aswell?). Many here will appreciate it, including myself. I like the software, I'd like to see it improve. I'm probably going to buy the windows version for my pc once it hits.
From what ive gathered on these past few pages of posts, i understand the descision to put this Instinctiv for maemo on hold is difficult but at the same time inevitable and understandable. Between being dissuaded from the present (maemo5) and being uncertain about the future (meego), it makes perfect business sense not to invest more time and money into this.
If you can, release the update you and your team have worked on for so long, with as much as you can implement (perhaps the new UI aswell?). Many here will appreciate it, including myself. I like the software, I'd like to see it improve. I'm probably going to buy the windows version for my pc once it hits.
|
|
2010-12-07
, 20:28
|
|
Posts: 227 |
Thanked: 51 times |
Joined on Feb 2006
|
#863
|
Pure fantasy but the win-win solution would go something like this:
Nokia realizes that its "schizophrenic" platform strategy has created hardship among both its user base and its developer base. As a show of good faith Nokia would pay to finish Instinctiv. The loyal Maemo user base gets thrown a bone for being patient and Nokia gets some good karma from the developer world.
Seriously, if $6000 would come close to covering the remaining development cost, it sounds like it would cost Nokia less than the equivalent of one full time employee to make finishing this product profitable for Instinctiv.
David
Nokia realizes that its "schizophrenic" platform strategy has created hardship among both its user base and its developer base. As a show of good faith Nokia would pay to finish Instinctiv. The loyal Maemo user base gets thrown a bone for being patient and Nokia gets some good karma from the developer world.
Seriously, if $6000 would come close to covering the remaining development cost, it sounds like it would cost Nokia less than the equivalent of one full time employee to make finishing this product profitable for Instinctiv.
David
__________________
David Smoot
David Smoot
|
|
2010-12-07
, 20:43
|
|
Posts: 147 |
Thanked: 472 times |
Joined on Jul 2010
|
#864
|
Originally Posted by CepiPerez
We did use QT and we did try to compile for Symbian^3. The most I can say is that it compiles -- the UI is badly broken as is a lot of our audio rendering and filesystem logic. Given the markets it's in, the people who use it and the longevity of the platform itself, building for Symbian is at the bottom of our priority list.
Did you use Qt for Instinctiv?
Did you try to compile this great app for symbian3?
This way you can sell the app for n8 and n900 and get the money you need to cover all costs.
We understand your disappointment and I hope you understand ours: we feel really frustrated to have worked this hard for nothing. The only thing we can really afford to do at this point is focus our attention on platforms where we can survive as a company.
|
|
2010-12-07
, 20:56
|
|
Posts: 147 |
Thanked: 472 times |
Joined on Jul 2010
|
#865
|
Originally Posted by djs_tx
There's opportunity cost for us. Time spent wrapping up the app in terms of salaries is somewhere on the order of $6k (a little more) or roughly two months of dev time to do everything we'd want to. But we could also spend those two months working on another platform or project and be making significant amounts of money two months sooner. Short of some kind of preload distribution deal on MeeGo I don't think there's much that could change our minds.
Pure fantasy but the win-win solution would go something like this:
Nokia realizes that its "schizophrenic" platform strategy has created hardship among both its user base and its developer base. As a show of good faith Nokia would pay to finish Instinctiv. The loyal Maemo user base gets thrown a bone for being patient and Nokia gets some good karma from the developer world.
Seriously, if $6000 would come close to covering the remaining development cost, it sounds like it would cost Nokia less than the equivalent of one full time employee to make finishing this product profitable for Instinctiv.
David
Start a petition
| The Following User Says Thank You to peter@instinctiv.com For This Useful Post: | ||
|
|
2010-12-07
, 21:18
|
|
Posts: 343 |
Thanked: 819 times |
Joined on Jan 2010
@ Paris, France
|
#866
|
@Instinctiv
this is an unfortunate end especially as you have so well understood this community
thanks anyway for what you brought and what you could bring from your latest development
this is an unfortunate end especially as you have so well understood this community
thanks anyway for what you brought and what you could bring from your latest development
 |
|
2010-12-08
, 09:10
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#867
|
Originally Posted by peter@instinctiv.com
The "actively discouraged" seems to have been misunderstood, so I'd appreciate a clarification. Can you describe in more detail the conversation? From this, it sounds like Nokia said "we suggest you do not provide any further releases for Maemo"; whereas from your other posts it sounds like Nokia told you sales volumes, that PR1.3 was the last release and that you did a perfectly fair & rational cost/benefit analysis and decided to draw it to a close.
Last week we spoke with Nokia. We were actively discouraged from developing for Maemo any further.
However, I'd hoped that even in the latter case, Nokia would have said something like "PR1.3 is the last release of Maemo, however we're committed to Qt - sticking to our preferred technologies and developing on Maemo will give you a headstart for the Harmattan device and other future MeeGo devices".
Further clarification would be much appreciated.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
|
|
2010-12-08
, 09:37
|
|
Posts: 156 |
Thanked: 29 times |
Joined on Jul 2010
@ Pakistan
|
#868
|
[QUOTE=bobcorn;891535]سلمان عباس :
طبعا
is that urdu or arabic?
طبعا
is that urdu or arabic?
|
|
2010-12-08
, 12:10
|
|
Posts: 35 |
Thanked: 246 times |
Joined on Feb 2009
|
#869
|
Originally Posted by peter@instinctiv.com
That's completely different than "discouraged from developing for Maemo" . If you look back to history, we announced LinuxTag 2008 that next Maemo platform, Harmattan will be Qt based so going to Qt is no longer any new issue. We had Qt for Maemo 5 since beginning, we supplied it with first beta SDK beginning of 2009.
That's pretty much the message we received.Originally Posted by attila77:
The Nokia message is still that Qt and Qt Quick are the transitional technologies from Maemo onto MeeGo. As I understand it, that is not the issue here - but rather the (monetization-wise) small userbase which is unlikely to get much bigger until the release of MeeGo devices.
Harmattan was at beginning called as Maemo6 and in practice going to MeeGo was in technical sense just renaming it. MeeGo was in practice merge of Maemo and Moblin and both of them were based on same components, so no major change were needed.
If you today develop for N900/Maemo5 using Qt, Qt Quick, Qt Quick Components and Qt Mobility, your application will run unmodified in MeeGo.
Nokia has given information about Maemo development directions a log time ago, we have also provided developer viesions of new technologies as early as possible so that any new technology won't become as surprise to developers.
Kate
|
|
2010-12-08
, 12:38
|
|
Posts: 35 |
Thanked: 246 times |
Joined on Feb 2009
|
#870
|
Originally Posted by peter@instinctiv.com
Let's make other clarification, Qt != QWidgets, QWidgets are UI components based on desktop paradigm and not well suited to mobile programming at all. We did a lot of work to make them working in Maemo5 but that's special one-of case. Don't expect other platforms to be same. To make good mobile UI you need to use toolkit designed for mobile US amd new mobile paradigm. Please read more from my blog: http://blogs.forum.nokia.com/blog/ka...ick-components
We did use QT and we did try to compile for Symbian^3. The most I can say is that it compiles -- the UI is badly broken as is a lot of our audio rendering and filesystem logic. Given the markets it's in, the people who use it and the longevity of the platform itself, building for Symbian is at the bottom of our priority list.
Kate
Did you try to compile this great app for symbian3?
This way you can sell the app for n8 and n900 and get the money you need to cover all costs.