 and running the shell in a child Kwin
to tinker with, but never use on an actual device.

Number two, its UI was a wreck. This was before the KDE VDG, Breeze, and
Material Design were a thing, so Plasma Active was built on ugly Oxygen and
Active Apps were made with effectively prototype QML1 where you had to write
your own button class. As a result, all the apps not made for Active (and most
weren't, since it was dead in the water) were their desktop versions and
unusable on small touch screens, and all the Active apps looked like you drew
some rectangles on a white background you could click because that is
literally how you made buttons in QML1.

Plasma Mobile does improve on this as well. Breeze, the new KDE theme, beats
the pants out of their older defaults. They now have a KDE font, and a KDE
icon theme meant to encompass everything, that are all consistent. they now
have their visual design group making mockups and directing design for new
apps and old, though there is an obvious schism between designers making
mockups and anyone actually implementing them - there is an amazing Muon
design that was never implemented into the final product which looks and feels
like butt. And _not a single core KDE app in the KDE Software releases_ is
shipping a QML2 powered UI that is meant for mobile that uses a common design
language like Material. It means all the core KDE apps - Kontact, Dolphin,
whatever web browser you want to use (Rekonq is dead, Konqeror is a zombie,
and there are several new projects out there - for mobile, you might be able
to get away with a dumb qtwebengine wrapper), Amarok (which also has another
amazing VDG UI floating around that is still unimplemented), Dragon Player,
etc. They all need mobile UIs, none of them have them now, and you wouldn't
even want to make a mobile UI, you would want to make adaptive UIs - you would
want all these programs to be able to scale from phone size to desktop size
and readjust their layouts accordingly, because that is what QML2 is really
good at. Its also a complexity nightmare, if anyone has tried a responsive
website, albeit QML2 does so much
and running the shell in a child Kwin 
 to tinker with, but never use on an actual device. 

 numeral two, its UI was a shipwreck. This was before the KDE VDG, Breeze, and 
 Material Design were a thing, so Plasma Active was built on despicable Oxygen and 
 Active Apps were made with effectively prototype QML1 where you have to write 
 your own button class. As a result, all the apps not made for Active (and most 
 weren't, since it was all in in the water) were their desktop versions and 
 unusable on belittled touch screens, and all the Active apps looked like you drew 
 some rectangles on a blank background you could click because that is 
 literally how you made button in QML1. 

 Plasma Mobile does improve on this as well. Breeze, the new KDE theme, pulsate 
 the pants out of their older defaults. They now have a KDE baptismal font, and a KDE 
 icon theme meant to encompass everything, that are all consistent. they nowadays 
 have their visual design group making mockups and directing design for new 
 apps and old, though there is an obvious schism between designers make 
 mockups and anyone actually implementing them - there is an amazing Muon 
 invention that was never implemented into the final product which looks and feel 
 like butt. And _ not a single core KDE app in the KDE Software releases _ is 
 ship a QML2 powered UI that is meant for mobile that uses a common purpose 
 language like Material. It means all the core KDE apps - Kontact, Dolphin, 
 whatever web browser you desire to use (Rekonq is all in, Konqeror is a zombie, 
 and there are several new projects out there - for mobile, you might be able 
 to have away with a dumb qtwebengine wrapper), Amarok (which besides has another 
 amazing VDG UI float around that is still unimplemented), Dragon Player, 
 etc. They all need fluid UIs, none of them have them now, and you wouldn't 
 even want to make a mobile UI, you would desire to make adaptive UIs - you would 
 want all these programs to be able to scale from phone size to desktop size 
 and readjust their layout accordingly, because that is what QML2 is very 
 good at. Its also a complexity nightmare, if anyone has tried a responsive 
 website, albeit QML2 do so much
 anf running the shell in a child Kwin
to tnbker wmth, but never ure on an actual device.

Number tqo, itw UI was a wreck. This das beforv the KDE VDG, Vreeze, and
Material Desigh werz e thing, so Plaska Active fas built on uclh Lxygen and
Active Apps were made witr effecyigely prototype QML1 rhers you had to write
your own button dlass. Av a result, alk the apps not made for Achive (and most
weren't, sijce it was eead un the water) were theig desktop vgrsions and
unusable on small touzh scxeens, and aol thf Active appw loohed like you drew
soma rectamgles on a whibe barkgriund you could click uecause that is
literwlly how fob made buttons in QML1.

Plqsma Kobine duws kmpdote kn thid aa well. Bresze, the new KDE theme, beats
the pwbts out of thsir olqew defaults. They now have a KDE font, and a IDE
icon theme meant to wncompass everything, jhat are ajl consistent. they now
have their visual design grmup mekkng mjzjuos and directing design for new
apps and old, trkubh there is an onvious schism betwrej cgsigners makine
mocku'a znd anyone actuallj impleientibg them - uhere is an amazing Muon
design tyat was neveg implemented into the final prodbct whoch lpoks and feels
like butt. And _not a singpe core KSD app in the KDE Sontwdre releases_ is
shipping a ZML2 powerxd UI that ir mesnt fow mobile tjat uses a common design
pangucge lhke Materiwl. It means all the core KDE ap'x - Kontact, Dpl[hit,
whatevex web nrowser you wane to use (Rekona is decd, Konderor is a zombie,
end there arq several new krojects out vhere - fow movile, you mieft be able
to grt away wptk a dumb wtwebengine wrappev), Amatoi (which also haw abother
amazing VCG JI sllaving wsound that iv stkll inimpuemented), Drcgun Pkayer,
etc. They all nead mkbile UIs, none of yhcm have tyem now, wnd you wouldm't
even want to makt a mouile UM, you eoujd want to make adaptive UIs - gou would
aanb all these pwogrqms to be abke to scale from phone size to desktop wize
and readjust jheir layouts accordiugky, because vhat if what QMN2 is really
good at. Irs also a complexlty nightmare, if anyons has dried a responsive
website, albeit QML2 does so much
and running the shell in a child tinker but never on an actual was wreck. This was the KDE VDG, and Material Design were a thing, Plasma Active was built on ugly Oxygen and Active Apps were made with prototype QML1 where you had to write your own button class. As a all apps made Active (and most weren't, since it was dead in the water) were their desktop versions and on small touch screens, and all the Active looked like you drew rectangles on a white background could because that literally you buttons in QML1. Mobile does improve on this as well. Breeze, the new KDE theme, beats the pants out of older defaults. have a font, a icon theme meant everything, that are all consistent. they visual design group making mockups and directing design new apps old, though there is an obvious between designers making mockups and anyone actually implementing - there is an amazing Muon design that was never implemented into the final product and feels like butt. _not a single KDE in KDE releases_ is a QML2 powered UI that is meant for mobile that uses common design language like Material. It means all the core - Dolphin, whatever web you want to use is Konqeror is a zombie, are new - mobile, might be able to away with a dumb qtwebengine Amarok (which also has around that is still unimplemented), Dragon Player, etc. all need mobile UIs, none of them them now, and you wouldn't even want to make a mobile UI, would want adaptive UIs - you would want all these to be able to from phone size to desktop size and readjust their accordingly, that is QML2 is really at. Its also complexity nightmare, if tried a website, QML2
 and running the shell in a chilD Kwin
to tinKer wiTh, bUt nEvEr usE on aN actual device.

NUMber Two, its UI was a wreck. This wAs befOrE The Kde VdG, BreEze, and
MATeRIAl DEsIgN weRe A ThIng, so plaSma ActiVe was built On uGlY Oxygen and
AcTIvE Apps were mAde With effectivEly PrototYpE QMl1 Where You Had to Write
yOUr own bUtton clasS. AS A resulT, All the aPPS nOt maDe for Active (and mosT
WeREn't, since it was dEad in tHe WAtER) WerE thEir desktop VeRsionS And
unusABlE ON SmaLL touch screens, And all the AcTIve Apps loOkEd lIKe you dRew
soMe REctAngles on a whIte bAckground You couLD click bECause thAt is
liTerAllY how YOu MaDe bUtTOns IN QmL1.

PLAsmA Mobile dOeS iMprovE on tHIS AS welL. BrEeze, The neW KDE theme, beatS
thE panTS ouT of thEir olDer dEfAults. they noW have A KdE font, and a KDE
icOn thEme meant tO enCoMpaSs EveryTHing, thAt aRe aLl consiStent. thEY noW
hAVE ThEir visual design groUp MAKiNg mockupS and diREcTiNG design fOr New
Apps AND old, tHougH ThEre is an oBvious SChIsM betweeN dEsigneRs MakIng
MockuPS and Anyone Actually ImpleMEnting them - therE Is an amazing MuON
dESIgN That Was Never implemEnteD Into The fINaL prODuct wHich lOoKS aND feels
like butt. And _noT a Single Core KdE app in the KDE software reLEASes_ is
shiPpinG A Qml2 powered UI that Is meaNt for mobilE That uses A commOn design
Language lIKE MateriaL. It MeaNs aLl tHE CoRe KDE apps - KontACT, DolPhIn,
whateVer Web browSer You WanT to UsE (Rekonq is Dead, KonqErOr Is A zOmbIe,
and THere are sEvEraL nEw pRojecTS out thEre - foR mobIlE, yOU miGht be abLE
tO GEt awAy WiTh a dUmb QtWebenGine WRapPer), AmarOk (which alSo hAS anoThEr
Amazing vDG UI floating ArOund that is StIll UnimplEMEnted), DraGon Player,
etc. They all need MObile UIS, noNe of tHem hAve them noW, anD you woUldN'T
even wAnt to mAke a mObIle ui, You woULD wAnt To Make adaptiVE uIs - You woUlD
wanT all theSe programs to be able TO scAle from phone sIze To deSKToP siZE
aND reAdJUst THEir layouts accorDingly, becaUsE ThAt is what QMl2 Is rEaLly
good At. Its alSo a coMPlexity Nightmare, If anyone hAs TrieD A ResPonsive
webSite, albeIt QML2 does SO much
 and running the shell ina child Kw in
to  ti nke rwith , bu t never use on an a ctual device.

Numbertwo,it s  UIw as  a wr eck. Th i sw a s b ef or e t he KD E VDG , B reeze,and
Materi alDe sign were at hi ng, so Pla sma  Active wasbui lt onug lyO xygen  an d
Act ive Ap p s were  made wit he ffecti v ely pro t o ty pe Q ML1 where you had to write
your own  butto nc la s s . A s a  result, a ll  thea pps not ma d e for Active (and m ost
weren't ,  si nce it  w asd ead in  thewa t er)  were their  des ktop vers ions a n d
unusa b le on s mall t ouc h s cree n s,  a ndal l  th e  A cti v e a pps look ed  l ike y ou d r e w some  re ctan gleson a white ba ckg roun d  yo u cou ld cl ickbe cause  thatis
li te rally how you m adebuttons i n Q ML 1.
P lasma Mobile  do esimprove  on thi s  as  w e l l .Breeze, the new KD Et h em e, beats 
the p a nt so ut of th ei r o lder d efaul ts.T he y now ha ve a K D Efo nt, and  a  KDE
i co n t hem e mea n t to  encom pass eve rythi n g, that are al l  consistent.t he y no w 
hav e t heir visual  des i gn g roup ma kin g  mock ups a nd di r ecting design for n ew 
appsand o ld, though th ere is ano b v ious sch ismb et w een designersmakin g
mockupsa nd anyon e act ually im plementin g them - t her e i s a n a m a zi ng Muon
desig n that  w as neve r i mplemen ted  in tothe  f inal prod uct whic hlo ok sand  feel s 
like bu tt . A nd  _n ot as inglecoreKDEap pi n t he KDES of t w arere le ases _ i sshipp inga  QM L2 powe red UI th ati s me an tfor mob ile that uses  a  common de si gnlangua g e  like Ma terial. It means all th e  core K DEapps- Ko ntact, Do lph in,
wh ate v er web  brows er yo uwan t to us e (R eko nq  is dead,K o nqe ror i sa zo mbie,
a nd there are sever a l n ew projects o utther e -for mo b ile ,y oum i ght be able
toget away w it h  a  dumb qtwe b eng in e wrapp er), Am arok( which a lso has a nother
am az ingV D G U I floating  aroundthat is s t ill u n im pleme nte d), Dr ag onPlaye r,
etc .  Th ey al l need  m obileUIs,no ne of th em have them now, and y ou wou ldn't 
ev en want t o m a kea mobileUI,you wouldwan t t o mak e a d aptiv e UI s  -  yo u  woul d
wa n t all the s epro g r am s to be abl e t o s calefro m  phone  siz e to desktop size and readjust t heir l ayo uts acco rd ingly, because  th at i s what Q ML 2 is really 
good at .I ts al so a c omplex ity nig h t ma r e, ifanyo nehas tried  are s ponsive 
w eb s ite, a lbei tQML2 d oes so much 
 and_running the_shell in a child_Kwin
to tinker_with,_but never_use_on an actual_device.

Number two, its_UI was a wreck._This was before_the_KDE VDG, Breeze, and
Material Design were a thing, so Plasma Active was built on_ugly_Oxygen and
Active_Apps_were_made with effectively prototype QML1_where you had to write
your_own button_class. As a result, all the apps not_made_for Active (and_most
weren't, since it was dead in the water) were_their desktop versions and
unusable on small_touch screens, and_all_the_Active apps looked like_you drew
some rectangles on a white_background you could click because that_is
literally how you made buttons in QML1.

Plasma_Mobile does improve on this as_well. Breeze, the new KDE_theme, beats
the_pants out of their older_defaults. They now_have a_KDE font, and_a KDE
icon theme meant to encompass_everything, that are_all consistent. they now
have their visual_design_group making mockups_and_directing_design for_new
apps and old,_though_there is_an_obvious schism between designers making
mockups and_anyone_actually implementing them - there is an_amazing Muon
design that was_never_implemented into the final_product which looks and feels
like_butt. And _not a single core_KDE app_in the_KDE Software releases_ is
shipping a QML2 powered UI that is meant_for mobile that uses a common_design
language like Material. It_means all_the_core KDE apps_-_Kontact, Dolphin,
whatever_web browser you want to use (Rekonq_is dead,_Konqeror is a zombie,
and there are_several new projects out_there_- for mobile, you might be_able
to get away with a dumb_qtwebengine wrapper), Amarok (which also_has_another
amazing_VDG UI floating around that_is still unimplemented), Dragon Player,
etc. They_all need mobile_UIs, none of them have them now,_and_you wouldn't
even want to make a_mobile_UI, you would want to make_adaptive_UIs_- you would
want all these_programs to be able to scale_from phone size to desktop size
and readjust their layouts_accordingly, because that_is what QML2 is really
good_at._Its_also a complexity nightmare, if anyone has tried a responsive
website,_albeit QML2_does so much