A lot of complaints

[atilacorreiacunha]

Ok, I can stand low revenues and low fillrates on ads partnerships.
Ok, I can stand troll comments not removed from my apps.
Ok, I can stand long QA analyses.
Ok, I can stand 30 days on a single e-mail response from QA for one single question.
Ok, I can stand tons of wrong e-mails with QA analyses like "Your app is not signed", even with my apps participating of Nokia Symbian Sign Beta program.
Ok, I can stand a lot of changes on platform focus, like "forget about Java/Flash lite, Qt for the win", and then BOOM, MicroNokia.

No, I cannot stand 180 days ( half fu**ing year ) to receive 300 euros of revenue.

[vladest]

hate this too, but this is reflected in agreement between you and Nokia and between Nokia and cell operators

[radeknati]

Is it so bad? Maybe it would be better to sell my app on my own - but first I should wait 180 days to earn 300 euros and buy Symbian Publisher ID for that money:-)

[vladest]

Is it so bad? Maybe it would be better to sell my app on my own - but first I should wait 180 days to earn 300 euros and buy Symbian Publisher ID for that money:-)

publisher ID costs 1 euro

[RomanAge]

publisher ID costs 1 euro

Is it so bad? Maybe it would be better to sell my app on my own - but first I should wait 180 days to earn 300 euros and buy Symbian Publisher ID for that money:-)

I think what radeknati meant is selling your app outside OVI. In which case the cost can be 0 euros (self-signed, just displays a warning message on installation). Only thing is unless you already have customers or lots of visitors to your website, I doubt it would sell much (no matter how good the content is).

[radeknati]

Yes, I meant selling app outside Ovi - but first I shoul buy certificate on symbiansigned.org and Publisher ID which costs 210$ (200 for ID, and 10 for app certificate) and then there isn't any warning message during installation. Does self-signed method need IMEI to each installation?

[pixsta]

Does self-signed method need IMEI to each installation?

No, it does not.

[Jon Heron]

Also, if your coding with Qt, it will cost 20 Euro for symbian signed, 10 for the app and 10 for the smart installer wrapper.
Jon

[pixsta]

But if you are distribution outside of Ovi store, then you are not forced to include smart installer; e.g. you could provide it as a separate package.

[vladest]

Also, if your coding with Qt, it will cost 20 Euro for symbian signed, 10 for the app and 10 for the smart installer wrapper.
Jon

gimme proovlink, pls

[radeknati]

I devolop in Qt. Could you tell me how can I self-signed my app using QtCreator? Which properties should I mark and where?

[Nokia Ron]

I devolop in Qt. Could you tell me how can I self-signed my app using QtCreator? Which properties should I mark and where?

Ask this on the Qt discussion board.

Ron

[Jon Heron]

gimme proovlink, pls

Sorry, I don't have a "proovlink". See the "Nokia_smart_installer_developers_guide.pdf if you want further info.
I am not speculating, but rather speaking from experience.
You must first sign the app, then wrap it in smart installer, then sign the entire package. If you submit your unsigned app to symbian signed wrapped in the smart installer you will receive an unsigned app inside of a signed smart installer, its a 2 step, 2 fee, process.
Pixsta, good point, but the other app stores I use dont allow links to off site downloads. That being said, I should make a formal request to allow a link to the Qt binaries... Cant hurt to ask...
Cheers,
Jon

[ltomuta]

I devolop in Qt. Could you tell me how can I self-signed my app using QtCreator? Which properties should I mark and where?

Qt Creator self-signes by default, and will do so for as long as you don't override its settings. Note however that self-signing is not possible if your application requires capabilities from the System, Restricted or Device Manufacturer ranges. See Capabilities and Symbian Signed info for more details.

[ltomuta]

But if you are distribution outside of Ovi store, then you are not forced to include smart installer; e.g. you could provide it as a separate package.

You could also embed Qt's sis files it in your application's package (but the package will grow huge) as long as to take the necessary precautions to avoid downgrading the installed version of Qt (if any).