Hacker News Reader

Comment by sebmaynard | Hacker News Reader

Here's a project the Beware team built, there's an iOS version built from the same source too

https://play.google.com/store/apps/details?id=com.keith_mage...

Also a note re their platform compatibility, it's not just Android and iOS: iOS, Android, Windows, MacOS, Linux, Web, and tvOS

Looks very interesting, going to give it a go adding guis to some existing cli python toys I've built

View on HN

Here’s the iOS version.

https://apps.apple.com/us/app/travel-tips/id1336372310

Looks pretty miserable. Are there any proper example applications or is this more of a toy framework?

Sorry to play the bad boy here.

But we have 2020 these 2 Apps (Android and iOS) are looking like websites from the 90s.

I don't get the point why everyone wants to add a framework to write one codebase and deploy on many platforms.

There are great working frameworks out here why we need the 100 framework doing this?

the last line of the comment you replied to gave a pretty good example: If you have tools build in tech X and just want to wrap them in a UI to make them usable on a phone. (similar to how Python ships with Tk bindings for UI: no, its not pretty, but it's an UI and thats what you want sometimes, without learning something big or worse a different tech stack)

> Looks very interesting, going to give it a go adding guis to some existing cli python toys I've built

and your python cli you want as bundled iOS/Android app? I don't buy it.

But anyway everyone has different problems and if this 1000 framework is solving this, congrats :clap:

Because everyone wants their preferred set of tools/languages to do it using the design patterns they like and there is nothing wrong with that. I don't see myself using Beeware ever really but that doesn't mean people shouldn't work on it.

Because if I can compile an iOS app in Python I don't need to give Apple (as much) money.

I mean, you’d still need to give them money for the dev tools if you happen upon some iOS specific bug.

Reply on news.ycombinator.com