[Interest] Modern

Fri Dec 21 17:34:23 CET 2018

+1
I'm writing software since 40+ years now and Apps for mobile devices
since 11 yrs
started with Qt/QML development for mobile Apps with QtQuickControls2
nearly 3 yrs ago.

have written my apps (same as Nuno Santos) ALONE

... without any knowledge of native Android or iOS development, also C++
was new to me.

comparing UI code of QML with Flutter: for me QML wins. code looks much
more modern and easy to understand.

last 3 yrs I have developed mobile business apps for Android, iOS (and
just also for Windows 10 Touchscreens):

  * around 10 example and conference apps available at github
  * a very complex (Dropbox-like) App for Enterprise to get access to
    shared network drives and SharePoints with all kind of
    share-with/from-other-apps on Android / iOS
  * a specialized Enterprise App for custom Bluetooth LE device to
    measure signal strength of different mobile network providers
  * a TimeTracking software for construction site managers
  * two very complex apps for care services: mobile with tour management
    and also inpatient care. with specialized Server-Queue Management to
    secure transport of patients data to server independent from
    offline/online state. highly specialized data entry for vital
    values, services, wounds with photos, ...
  * a EAN 13 - Barcode Scanner App, checking with server if Barcode is valid
  * a Goods issue control app for Plant Wholesale with BT LE Barcode
    Scanners
  * a Goods receipt app for Plant Wholesale with BT LE Barcode Scanner
    and mobile Printer
  * next app in work for Property Managers ...

I don't know of any other development framework enabling me to do this
ALONE x-platform with native speed.
Customers like my apps because of great UX and good performance (doing
all business logic and complex UI logic in C++)

so for me Qt/QML with QQC2 is a really modern development environment

thanks to the teams at Qt

ekke

Am 20.12.18 um 15:23 schrieb Nuno Santos:
> Hey Roland,
>
> Sorry mate.. I couldn’t avoid... 
>
> How are you writing UIs this days? What is modern to you?
>
> I consider myself young. I’m only 36. But I have been writing software for the last 20 years.
>
> In the last 6 years I have written 4 different apps ALONE! One of them was written 3 times. One in native iOS, then in native Android and then in Qt Qml.
>
> Qml is by far the BEST way I have ever used to write a UI! 
>
> UI code is glue, glue, glue. Every single other framework requires so much code to do exactly the same things as with Qml.
>
> Qt/Qml allowed me to advance at least 5x faster than any other UI framework.
>
> Is perfect? Nothing is perfect! There is are always pros/cons.
>
> Any way... for me, Qml in terms of UI writing is so modern that stands that easily stands from any other technology around.
>
> I want to express my gratitude to the WHOLE Qt team to make it possible! You guys rock! Qt Quick is definitely one of the best things around there.
>
> Best regards,
>
> --
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt
>
> No dia 20/12/2018, às 13:26, Roland Hughes <roland at logikalsolutions.com> escreveu:
>
>> It's still not modern.
>>
>> Modern implies "something which learned from past mistakes to overcome many of them." When something recent fails we simply call it "a new approach" implying that it failed, generally beyond human comprehension. Modern implies something succeed in overcoming many/most/all of the pitfalls/travesties/tragedies which came before.
>>
>> The latter does not apply to QML.
>>
>> Newer isn't better, just newer.
>>
>> Some "light" reading.
>>
>> https://www.cbinsights.com/research/corporate-innovation-product-fails/
>>
>> How many of you writing idiot phone apps know their used to be a Facebook Phone? A Ubuntu Phone? There even used to be an Apple Newton.
>>
>> Now that pretty much every industry analyst agrees the fad of idiot phones are over and that 2019 will be the first year of negative growth for the industry, scripted UIs will die off with them. Five years from now people will think about QML as often as you currently think about the Apple Newton.
>>
>> More light reading:
>>
>> http://www.interestingauthors.com/blog/thankyousirmayihaveanother/the-counter-culture-has-won/
>>
>> Hopefully you all read far enough in the first link to read about Amazon's colossal failure, The Fire Phone. Even I didn't know Microsoft tried to market a "smart watch" in 2004. That thing must have only been on the market a few minutes!
>>
>> Be sure to scroll down to #35. Microsoft Kin One and Kin Two. Discontinued after 6 weeks. No wonder I'd never heard about this wanna-be Blackberry.
>>
>> Oh, from your own link
>>
>> /Although it was built in the 1600s, the building still has a very *modern* look./
>>
>> /
>> /
>>
>>> On 12/19/2018 12:33 PM, Ian Trick wrote:
>>> On Tue, Dec 18, 2018 at 6:15 AM Roland Hughes
>>> <roland at logikalsolutions.com> wrote:
>>>> QML is __NOT__ modern.
>>> modern: Pertaining to a current or recent time and style; not ancient.
>>>
>>> https://en.wiktionary.org/wiki/modern
>>>
>>> 🤔
>>>
>>>>>> On 17 Dec 2018, at 16:44, Fabrice Salvaire<fabrice.salvaire at orange.fr>  wrote:
>>>>>>
>>>>>> Dear Qt users,
>>>>>>
>>>>>> Is there people around who needed to hack QQuickTextNode private API ? IMHO it restricts strongly the possibility to develop modern custom QML items.
>> -- 
>> Roland Hughes, President
>> Logikal Solutions
>> (630) 205-1593
>>
>> http://www.theminimumyouneedtoknow.com
>> http://www.infiniteexposure.net
>> http://www.johnsmith-book.com
>> http://www.logikalblog.com
>> http://www.interestingauthors.com/blog
>> http://lesedi.us
>>
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> https://lists.qt-project.org/listinfo/interest
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181221/dc55c55e/attachment.html>