The current use by 20 apps in the store:
- 2 apps that cannot be ported as of today
- one app that would require a sizeable amount of work
- one app that would require some work
- 5 apps that would require minimal changes
- 11 apps that wouldn’t require any changes (other than the imports)
(9) no specific QtWebKit API used, can be replaced by Ubuntu WebView without any changes:
com.ubuntu.developer.bobo1993324.udropcabin
com.ubuntu.developer.carloalberto.randomimagesrel
com.ubuntu.developer.fabricio.mnmo-counters
com.ubuntu.developer.hansueli.burri.xkcd-viewer
com.ubuntu.developer.larochelle.brian.feed-the-aggregator
com.ubuntu.developer.mlosli.panpipe
com.ubuntu.developer.mzanetti.getmewheels2
com.ubuntu.developer.yuntan.aztter
ir.oneapp.oneperday
(2) actually uses an UbuntuWebView (version 0.1), can be replaced by Ubuntu WebView without any changes
com.ubuntu.developer.mzanetti.ubuntu-fitbit-app
com.ubuntu.developer.rschroll.beru
(1) uses onLoadProgressChanged, but can easily be rewritten to avoid that
fr.skimbo.skimbou
(1) relies on the fact that QtWebKit’s WebView is a flickable, shouldn’t be too hard to port to Ubuntu WebView
com.ubuntu.developer.brianrobles204.karma-machine
(1) uses lots of QtWebKit experimental APIs (it’s a browser app), sizeable amount of work to migrate to Ubuntu WebView (or more likely a raw Oxide WebView)
com.ubuntu.developer.penk.slatekit-shell
(2) uses QtWebKit experimental APIs such as urlSchemeDelegates, cannot be replaced by Ubuntu/Oxide WebView as is
com.ubuntu.developer.dpniel.dekko
com.ubuntu.developer.zaspire.cordova-mobilespec
The current use by 20 apps in the store:
- 2 apps that cannot be ported as of today
- one app that would require a sizeable amount of work
- one app that would require some work
- 5 apps that would require minimal changes
- 11 apps that wouldn’t require any changes (other than the imports)
(9) no specific QtWebKit API used, can be replaced by Ubuntu WebView without any changes: developer. bobo1993324. udropcabin developer. carloalberto. randomimagesrel developer. fabricio. mnmo-counters developer. hansueli. burri.xkcd- viewer developer. larochelle. brian.feed- the-aggregator developer. mlosli. panpipe developer. mzanetti. getmewheels2 developer. yuntan. aztter oneperday
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
ir.oneapp.
(2) actually uses an UbuntuWebView (version 0.1), can be replaced by Ubuntu WebView without any changes developer. mzanetti. ubuntu- fitbit- app developer. rschroll. beru
com.ubuntu.
com.ubuntu.
(4) uses WebView. onLoadingChange d, minimal changes needed stems.app. freshbookstimer developer. mitya57. touchwriter developer. qqworini. aesyweibo developer. qtros.twimgo
com.nucleussy
com.ubuntu.
com.ubuntu.
com.ubuntu.
(1) uses onLoadProgressC hanged, but can easily be rewritten to avoid that
fr.skimbo.skimbou
(1) relies on the fact that QtWebKit’s WebView is a flickable, shouldn’t be too hard to port to Ubuntu WebView developer. brianrobles204. karma-machine
com.ubuntu.
(1) uses lots of QtWebKit experimental APIs (it’s a browser app), sizeable amount of work to migrate to Ubuntu WebView (or more likely a raw Oxide WebView) developer. penk.slatekit- shell
com.ubuntu.
(2) uses QtWebKit experimental APIs such as urlSchemeDelegates, cannot be replaced by Ubuntu/Oxide WebView as is developer. dpniel. dekko developer. zaspire. cordova- mobilespec
com.ubuntu.
com.ubuntu.