Combining Symbian and Qt API's for mobile app development
summary
Teleca reports building multiple Qt apps including a music player with real-time mixing and live streaming but finds that Qt covers over 90% of app logic while native Symbian APIs are required for audio mixing, telephony, flight mode, volume-key capture, camera context, profiles and cryptography. Fifteen teams contribute concrete fixes: RemCon for keys, CTelephony and active objects for calls/flight mode, APATask for launching apps, and a PIMPL pattern to keep Symbian code isolated.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 2:16About Teleca and its work
- 5:50Qt vs Symbian development comparison
- 7:32Qt API limitations and gaps
- 10:21UI and input control issues
- 15:21Native menu and app launch problems
- 18:28Camera, profiles and app list access
- 21:42Virtual keyboard and web services
- 26:41Audio mixing and codec support
- 28:08Mixing Qt and Symbian code
- 34:08Data type conversions
- 35:35Symbian device compatibility
- 37:19Developer resources and solutions
- 37:41Conclusions and final remarks
- 39:25Q&A session