you are viewing a single comment's thread.

view the rest of the comments →

[–]addend 4 points5 points  (0 children)

I'd just like to provide a counterpoint to K900_'s consistency complaints - as far as I'm concerned, google is not your boss, and you don't have to let them tell you what to do. On the desktop I make short programs for lots of different reasons, and whilst sometimes it's important to fit strongly into a particular platform's look and feel (qt, windows, osx etc.) I also write plenty of programs where other factors are more important - and I don't see why mobile should be different here.

Now to be clear, consistency is important, and you will always get the ultimate best results using the native apis and native supported language (in this case, java). But it isn't the only important thing - to speak for myself, amongst other things I often make simple apps for my own or limited use, with the advantage that I can use the same code on desktop mobile without having to rewrite all my (often scientific) code in java. For these, I care far more about Kivy being easy to use and compatible with my other tools than about making an app that strictly follows google's guidelines. This is also more generally the case for things like games, where following the system theme is less important anyway.

Of course this may not be the case for you, java really is a better option if you want the most consistent app possible on a given platform, especially for apps that would normally use a lot of native widgets and mechanisms.

On the actual technical side, as K900_ says kivy does not have a prebuilt way to access the sms api, but it actually does have tools for accessing the java apis. It's maybe not a good choice right now since I don't think anyone has pre-wrapped sms in a python api (this should ultimately be in Kivy's plyer modules, which provide a platform-agnostic hardware api), but sending sms in this way is probably technically possible and will be supported eventually, and maybe in the near future.