Yes, Ivy recently passed review. UI code is native, business logic is Go.

https://itunes.apple.com/us/app/ivy-big-number-calculator/id...

This is what I want to see more of, I get very worried about any tech claiming to overtake the UI layer of your application and make it cross platform. It never makes sense to do IMO. Logic and models though however, I can't wait!

Couldn't agree more on this. And hopefully there are a enough examples now to show why it simply doesn't work.

If you can't be bothered to fully embrace the design approach of the host platform e.g. Material Design then don't expect your users to be bothered to download your apps. Because most people appreciate that their apps look and feel like a true native app and not some cross platform version that was designed to put the developers first and the users second.

People don't want to get locked into a proprietary interface.

Doesn't chrome and firefox finesse the target interface and rely on a portable C/C++ core?

How are they doing this? Is there some "transform" into C to use a subset of "objective c" going on?

Way back in like 2010 there was a clause added briefly to the iOS developer guidelines saying things had to be in Objective-C. There was an outcry and it disappeared not long afterward. Unfortunately, the idea that other languages can't be used persists. Shows how much damage a dumb political mistake can have, even if it's quickly walked back.

They are using this package https://godoc.org/golang.org/x/mobile/cmd/gobind to generate the libraries and bindings for objective c and java.

"NOTE: iOS support is not ready yet. " [ https://godoc.org/golang.org/x/mobile/cmd/gomobile ]

?

It works if you build from tip. Definitely not polished though.

iOS has a surprising number of realistic language choices, where by "realistic" I mean a savvy end-user would never know you didn't use Objective-C (so, PhoneGap & co are not counted).