First of all, I congratulate everyone and thank you for your interest in my question.
I am currently working on a mobile launch. Our product is a communication application for Android, iOS, and BlackBerry devices, and we strive to expand it on some Nokia platforms.
I donβt know much about the details of Symbian, as I have never programmed them on the platform before, but this is all the information I could collect.
Support platforms are Symbian S60, Symbian ^ 3 / Symbian "Anna", Maemo + Meego.
To achieve this, we have several tools at our disposal, but we are not sure which ones to use.
Nokia Qt is not supported on Symbian S40 devices (we seem to be stuck in J2ME) and Symbian S60 devices until the 3rd release of Feature Pack 1
In Symbian C ++, we cannot rely on C ++ STL. This means that we can either create two versions of the same software, or create our own STL compatible with Symbian (I would like to avoid this).
An approach
Among the team, consensus seems to be to split it into two logical fragments:
- Basic business logic + C ++ libraries
- Fixed UI branches using Qt or custom UI tools.
With all this information in mind, I ask:
What is the general approach to this problem? Are there any significant flaws in the above, namely: incompatibility or inconsistency with Qt on older platforms?
What mistakes should we avoid in order to ensure application compatibility and performance in all of the listed Nokia devices?
Is there a way to get around the limitations of Symbian C ++ for STL? Can we somehow relate the sources of Qt?
Suggestions and other approaches are welcome. Thank you for all your feedback.
source share