Spreading Ubuntu Touch to the world



  • Maybe contact the developers of Instagram, WhatsApp, Twitter, etc and see if they are interested in writing apps for Ubuntu Touch? Making Anbox an easier install would also help.

    Personally I am posting screenshots of Ubuntu Touch to all my social media profiles in the hope of spreading the word about the OS.



  • @ernmander
    Would be really a great move, if you can contact them and tell us what was the result.
    I contact WhatsApp already August 6th 2015, about that concern. The only answer was a standard answer:

    Hi,

    We apologize that we have not gotten back to you yet.

    If your inquiry is a feature request, please understand that we have received your request and our development team is constantly working to improve our product. However, due to the small size of our company we are currently unable to supply a timeline for any feature.

    If you are still experiencing the issue you wrote in with, please first follow these steps:
    ......

    There was no other response anymore....



  • Should partner with electroneum!

    They are making phones now. Cryptocurrency is is about decentralized and freedom might as well make it open source.


  • Community

    @bencozzy

    We're not interested in partnering with any cryptocurrency right now. If you only registered to advertise an online currency I don't think you'll get very far here. 🙂



  • @bencozzy Hi, This thread is about spreading the Ubuntu Touch word. Please can we not get distracted with bringing cryptocurrency into the debate.


  • Infrastructure

    @WLBI with the upcoming phones I really expect that things will change then.

    While Purism is at the upper segment and therefore probably not for people who want to try out, I see lot of potential for advertising UT with the Pine phone. It will be in a reasonable price range, and especially for our app devs its important to get real hardware so they can work. Remember we do not have a working emulator or SDK, so its superhard to develop Apps.



  • @Flohack said in Spreading Ubuntu Touch to the world:

    Remember we do not have a working emulator or SDK, so its superhard to develop Apps.

    TBF, it's not so hard, if you build a qqc2 app. However, there does seem to be some issues in the stack when running on a device, which don't appear under X11 qpa with Qt. It seems to be related to initial sizing of components in the QML, and partly depends on how they are constructed in the QML.

    Am still banging my head on some of this, but it seems like maybe less of a problem if using Qt's autoscaling by enabling it in a main.cpp before initializing the app engine. So it's possible to develop an app on say stock Ubuntu 18.04 which works fine there with Qt 5.9.5, and then package it with clickable into a click for UT.


  • Infrastructure

    @dobey I mean rather the lack of all APIs, like sensors, camera etc. Modern Apps want to use that stuff, of course, and thats much easier for hobbyists or part time developers if they can just a real device.

    Emulation, cross-development etc. is all possible, but comes at a cost, and we want to have the lowest possible barrier ofc.



  • Instead of thinking of a whole SDK, we could start by providing docs on how to get auto completion and code navigation for some editors, as well as docs on how to debug apps. Imo we would have achieved a lot already then (together with clickable and the docs we already have).



  • @Flohack said in Spreading Ubuntu Touch to the world:

    @dobey I mean rather the lack of all APIs, like sensors, camera etc. Modern Apps want to use that stuff, of course, and thats much easier for hobbyists or part time developers if they can just a real device.

    The sensors and camera APIs are standard Qt APIs in QML. For example, I use authenticator-ng (qqc2/ergo version) daily on my PC. The camera usage in it works fine, as long as I have a webcam plugged in, or use it on laptop with built-in camera. Granted, there are plenty of things like content-hub which won't work without the pieces being available, but building a pure qqc2 app works just fine, as I said.

    Emulation, cross-development etc. is all possible, but comes at a cost, and we want to have the lowest possible barrier ofc.

    The whole point of unity8's goal of convergence is that the apps are built to run everywhere from the same source tree. You don't need, cross-compiling, etc… to develop apps, only for building to deploy. The barrier for developing apps for UT is extremely low, we just haven't made it apparent. If you want to lower it further, the best ways I see to do that are to focus on making convergence a reality, documentation, and then the deployment issue.


Log in to reply