non-native

The sentiment is clear, but the word choice is typical of a non-native speaker finding something that probably sounds about right, and will probably get the message across.

Oh, and the Mac/OSX people will be angry you try to get them to force them to use too many non-native GUIs.

Poorly designed apps, non-native apps, heavy Javascript frameworks, ad popups etc.

As a non-native speaker I only find the pun when someone says it's pun.

You can implement the platform accessibility APIs for a non-native UI, but it's a lot of work; just ask the relevant developers of Chrome and Firefox.

As a non-native English speaker, I am so encouraged to see your approval.

For non-native viewers it is a really nice addition.

And we continue to maintain non-native IO and process logic for limited environments.

I have heard rumors that this narrowing of vocabulary may be intentional, in order to make English-language media more accessible to non-native speakers.

There are also some non-native client apps (like Chrome) that I think (admitting my bias in Chrome's case) do a pretty good job.

As soon as you try that, you end up compromising the UX with either non-native UI components, or lowest common denominator APIs that try to bridge iOS/Android.

As a non-native speaker this sentence seems odd.

To non-native English speakers, particularly it seems continental Europeans, it is generally taken to mean "company has offered to consider you for a job" (as opposed to you approaching them).

Certain things, like the "open file" dialog, really suffer if they look non-native.

As a non-native, it took me some time to grok that the term "drugs" can mean both "medicines" (like aspirin) and "addictive substances" (like alcohol, tobacco or cocaine).