Results 1 to 3 of 3

Thread: Comparing Qt Mobile with native mobile development

  1. #1
    Join Date
    Sep 2009
    Location
    Aachen, Germany
    Posts
    60
    Thanks
    2
    Thanked 7 Times in 7 Posts
    Qt products
    Qt4
    Platforms
    Windows

    Default Comparing Qt Mobile with native mobile development

    Hi everyone,

    I work for a company that develops its products with Qt/C++, but in the near future we plan to create apps, both for Android and iOs.
    I've had some personal experience using the Android SDK while creating a few small apps for myself.

    I've been discussing whether we should use Qt Mobile oder native SDKs with someone at work on and off for a while now. He argues that with Qt Mobile we just have to build the app once, using a SDK we know well. While that's perfectly true I think that there are just too many drawbacks:
    • The user will need Qt, making the app much larger than neccessary
    • We either have a generic look and feel for all platforms or have to create different UIs to recreate native look and feel, which is, I think, very important
    • Whenever there are platform changes we will have to wait for the Qt Team to integrate them into Qt Mobile
    • As this will be a client-server App there really won't be much going on besides the UI
    • I'm a little worried about performance on older phones
    • We don't have any experience with Qt Quick and, to be honest, I don't really care for it


    So, my question is: What do you prefer, Qt Mobile or native development, and why?

  2. #2
    Join Date
    Jan 2006
    Location
    Graz, Austria
    Posts
    8,416
    Thanks
    37
    Thanked 1,544 Times in 1,494 Posts
    Qt products
    Qt3 Qt4 Qt5
    Platforms
    Unix/X11 Windows

    Default Re: Comparing Qt Mobile with native mobile development

    That all depends on a lot of factors.

    As you said there are drawbacks like package size when using Qt.

    Obviously there are also drawbacks when using native SDKs.
    For example if you don't already have skilled Java and Objective-C developers, then using the respective native SDKs would require new hiring or training.

    If the application has any logic despite UI then sharing the same logic across platforms will lead to more consistent behavior and reduce maintenance costs (bugs only need to be fixed once).

    Neither approach requires having the same generic interface nor requires to have different interfaces.

    Cheers,
    _

  3. #3

    Default Re: Comparing Qt Mobile with native mobile development

    Qt exists since more than 20 years and supports many platforms. Now Qt can be faster on ios and android than apps done with their respective native apps. So Qt is the better one.

Similar Threads

  1. Mobile App Development with Qt 5.3
    By juracist in forum Newbie
    Replies: 1
    Last Post: 8th August 2014, 06:11
  2. Mobile application development
    By Rocksteady in forum General Programming
    Replies: 0
    Last Post: 11th September 2012, 12:25
  3. Future of Qt Mobile
    By been_1990 in forum General Discussion
    Replies: 0
    Last Post: 5th July 2011, 00:26
  4. mobile extensions problems in Qt mobile app
    By hasnain in forum Qt for Embedded and Mobile
    Replies: 0
    Last Post: 31st December 2010, 11:29
  5. How to put app to mobile?
    By erdomester in forum Qt for Embedded and Mobile
    Replies: 2
    Last Post: 16th May 2010, 14:15

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.