There are pros and cons with any technology choice; whether using Kivy is a good fit for your project depends on your current skill set, what you want to learn, what you want to accomplish, and so on. Nobody else knows the answer for your situation, including the Kivy naysayers in other comments. There is nothing stopping you from adding auth, login, or whatever you need in the future, but obviously you will need to do it within the Kivy ecosystem, and it has has some limitiations. You may need to do extra work like write wrapper code or modify your build process to use specific libraries which are made for native apps, or depend on compiled code, and so on.. Almost anything can be done, but depending on how deep it is, you may need advanced knowledge of the underlying tech or p4a/kivy-ios, or the platform-specific build toolchains etc. Kivy apps are the same as native apps in terms of how you need to handle versions, releases, etc towards the platform (but the build process to make the .APK/.IPA are different), it mostly boils down to how you write the application code and how you compile it. Edit to add: To me, the biggest downside of Kivy in terms of mobile platforms is the complex build toolchain that in some cases is a bit hacky. There is no warranty that it will keep working with future updates of Android/iOS , although it's been mostly functional for a decade, and afaik there is no reason to think it will stop working... but still, it would worry me for a serious project. For hobby stuff, no big deal. More on reddit.com

Kivy is not designed for game design. It's designed for standard everyday apps. The impression might get caused by kivy mostly showing games in the gallery, but that's just because a lot of users like to create games. Has nothing to do with the intention of kivy itself :) Another reason why a lot of people think that kivy is heavily designed for games is that it uses pygame as a background service. Most users don't know that kivy just uses pygame to draw on a window. It doesn't even give you the ability to use pygame features yourself. It's basically just a background provider for a drawable surface!

The only problem I see with using kivy for everyday apps is the slow startup. That might be a reason to develop the app in a different language (especially when it's supposed to be an app that you open and close very often each day)

So:

• Apps that get opened/closed really often -> Might consider switching to a different framework/language. Perhaps the native Java app thing.

• Apps that you open less often (so you can live with the startup time) or if you don't care about the startup time: use kivy!

More on reddit.com

Yes.

More on reddit.com

I figured I would post this in Kivy subreddit later, but I'm currently working on a mobile app in Kivy in my spare time. I've got the core application logic done so far and all that is left is 1)spit-shine-polish the interface 2)incorporate ads and 3)package Android/iOS. It's been pretty painless so far, but the worst may be yet to come. I've found some resources much more helpful than others. If I had to recommend three resources for learning/using Kivy they would be: 1) http://kivy.org/docs/gettingstarted/examples.html ->A list of all the examples that come included with the Kivy install. It's been unbelievably helpful to search the page for roughly what I'm looking for and then open up the corresponding example. This saves me a lot of time and means I don't have to guess my way through 30+ examples to find the one I want. 2)This blog: http://karanbalkar.com/tag/kivy/ ->Having not done GUI programming in a long time, this blog really helped me. It's filled to the brim with a number of good, simple, and useful examples. I'd recommend this for anyone trying to create an app in Kivy. 3) The Google Group. https://groups.google.com/forum/embed/?place=forum/kivy-users#!forum/kivy-users ->Odds are good that someone has already asked the Kivy question that you have floating around in your mind. Searching the group has yielded some invaluable information about Kivy specifics and the future of Kivy development. More on reddit.com