Application Development Approach on Many Nokia Devices

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.

+6
source share
3 answers

There are versions of STL that can be used on Symbian. I was once part of a team hat using the C ++ kernel (with STL) on Symbian devices from S60v1 to S60v5, as well as UIQ, S80, and S90. The same core was also used on Windows mobile devices. We used STLPort to implement STL, but I could not find this particular version again. I really believe that there are other implementations of Symbian STL.

The S60, on the other hand, has a very competent J2ME runtime, so if you need to develop a J2ME application for S40 devices, you can also use it on the S60.

0
source

You must bear in mind that Symbian is a dying platform, so I will not put a lot of effort into developing the Symbian application. And even more so, I would not use Symbian C ++. Qt is a promising platform, but Nokia / Microsoft has announced that there will be no Qt port for a Windows phone (which may be interesting for you). Perhaps you should only support Nokia Java Java ME devices, because Symbian has a large market share, but most devices are not smartphones where you can run the Qt application.

Your approach sounds very idealized, but I'm not sure if you can use the C ++ libraries mentioned for the Java ME business logic. Is it possible?

+2
source

I have no more experience like you, but in my opinion, Qt is good for application development. Write code once to target multiple platforms. Qt allows you to write advanced applications and user interfaces once and deploy them on desktop and embedded operating systems without overwriting the original time and development cost. Thanks

0
source

Source: https://habr.com/ru/post/890568/


All Articles