Kivy: Cross-Platform Python Framework for UI Development
1–10 of 59 posts
Re: Kivy: Cross-Platform Python Framework for UI Development
#2For example, stick to the basics and it works well. But do something off the beaten track like write a background service for Android and hit a bug and you're completely on your own, even if you offer to pay a core dev. I once hit another bug where Unicode couldn't be used in .kv files, was a one line fix but there were 70 unread pull requests and more even more issues untouched. Two or three heros try to help on the mailing list. I gave up but would like to try one more time with 2.0.
Re: Kivy: Cross-Platform Python Framework for UI Development
#3The question is, who actually uses these projects? The people developing them? Hobbyists? Language diehards? If you're a large company that just needs LOB apps, one would assume one of the aforementioned projects (or Delphi) would be sufficient. Who uses NativeScript, Ionic, QT on mobile, or obscure stuff like Sencha, Alibaba's Weex or Codename One?
RubyMotion at least has one famous app:
http://www.rubymotion.com/news/2014/04/08/rubymotion-success...
Re: Kivy: Cross-Platform Python Framework for UI Development
#4It's quite fascinating to read about mobile crossplatform projects beyond React Native/Flutter/Xamarin and the old Cordova/PhoneGap and Appcelerator Titanium efforts. There's a surprising amount of them out there- Kivy isn't even the only one in Python, there's also Beeware ( https://www.youtube.com/watch?v=qaPzlIJ57dk ) and PyMob. The question is, who actually uses these projects? The people developing them? Hobbyis…
Re: Kivy: Cross-Platform Python Framework for UI Development
#5Kivy is awesome considering what it,s trying to do. As ambitious as flutter but without corporate support. Unfortunately the project is quite under-resourced, can anyone help? For example, stick to the basics and it works well. But do something off the beaten track like write a background service for Android and hit a bug and you're completely on your own, even if you offer to pay a core dev. I once hit another bug w…
Re: Kivy: Cross-Platform Python Framework for UI Development
#62) I prefer tkinter, a python wrapper for tk.
3) In regards to whether or not anyone still needs this, consider that tkinter search traffic bottomed out in June 2012, and has been rising ever since: https://trends.google.com/trends/explore?date=all&geo=US&q=t...
Re: Kivy: Cross-Platform Python Framework for UI Development
#7Re: Kivy: Cross-Platform Python Framework for UI Development
#8So, I’m not sure whether the website was made using the product, but the homepage renders overlapping text on Chrome for IPhone 11 with IOS 14
Re: Kivy: Cross-Platform Python Framework for UI Development
#9It's quite fascinating to read about mobile crossplatform projects beyond React Native/Flutter/Xamarin and the old Cordova/PhoneGap and Appcelerator Titanium efforts. There's a surprising amount of them out there- Kivy isn't even the only one in Python, there's also Beeware ( https://www.youtube.com/watch?v=qaPzlIJ57dk ) and PyMob. The question is, who actually uses these projects? The people developing them? Hobbyis…
Great UI has diminishing returns that, for most orgs, are not worth the talent and effort it takes to create them. For that reason investment in these frameworks, or new frameworks at all, is discouraged. Web based approaches have completely supplanted native || crossplatform frameworks because its good enough and established enough to diminish the many development liabilities that other frameworks pose.
Re: Kivy: Cross-Platform Python Framework for UI Development
#10It's quite fascinating to read about mobile crossplatform projects beyond React Native/Flutter/Xamarin and the old Cordova/PhoneGap and Appcelerator Titanium efforts. There's a surprising amount of them out there- Kivy isn't even the only one in Python, there's also Beeware ( https://www.youtube.com/watch?v=qaPzlIJ57dk ) and PyMob. The question is, who actually uses these projects? The people developing them? Hobbyis…
Great UI has diminishing returns that, for most orgs, are not worth the talent and effort it takes to create them. For that reason investment in these frameworks, or new frameworks at all, is discouraged. Web based approaches have completely supplanted native || crossplatform frameworks because its good enough and established enough to diminish the many development liabilities that other frameworks pose.
Your point on web based approaches also doesn't seem to match reality yet as PWA are still the once and future destiny of mobile apps, much like \(currentYear) is the year of Linux on the desktop. afaik, it would seem like most mobile apps are still primarily native, and if crossplatform, possibly React Native or Xamarin, with some older ones using Cordova/PhoneGap/Titanium. Web based approaches are far from replacing native and cross-platform; most companies that support mobile web also have their own apps.