Important: Please read the Qt Code of Conduct -

Writing the least amount of different source codes for a mobile app + web site

  • Hi all,

    I want to create an application which will need a website as well.
    What I'm looking for is how to make as few different source codes as possible. My definition for a "source code" is a code for a single platform/service.
    What needs to be done is as follows:

    1. Mobile app - there's a need for: iOS version, Android version, Windows phone version, web service, database.
    2. Website - client and server side, database.

    My priorities are from highest to lowest:

    1. As few source codes as possible.
    2. Fastest learning curve as possible for my knowledge (will be described next)
    3. Cheapest.

    My knowledge: C#, Java, Native Android, a bit of Spring, a bit of PHP, a bit of MySQL.

    If there's a need to learn some technologies - for example ASP.NET, HTML, CSS, Javascript - I'll do it. I heard you can somehow create a web site and then turn it into a cross platform mobile application like PhoneGap or Ionic, which means you might be able to get a single source code for everything - is it true?

    What do you think is the best option in my case?

  • To use Qt wouldn't you want to know C++? Qt could then compile to all your targets, your problem comes in writing the database and website, you could use HTML and CSS and some form of database but I hear a lot of good things about Ruby on Rails but the choice is up to you. If you are only compiling the program for android and having a website for everything else there would be no cost. It seems to be commonly accepted that compiling dynamically for mobile does not require a license, and the only fee's left would be for whatever you potentially host your website on.

  • @RobertoDuran QML is the preferred option in Qt for mobile apps (assuming the app isn't really complicated). QML is pretty easy to grasp with some background in JS.

    @devOp well, as this is the Qt Forum, I need to say that Qt is the best option :)
    Of course you can do the described project in many ways. What is best really depends on what you want out of the project. Are you looking to learn something new? Do you just have to push it out as fast as possible? Do you need to maintain it (this is honestly the biggest workload)? How complicated is the app, what resources does it use on the mobile?

    Lot's of questions, so it really depends, but Qt will provide a solution to all the mobile platforms with a farily easy learning curve and a good community that can help out when you run into trouble.

Log in to reply