‘Silver’ lets developers to use Apple’s Swift to write Android, Windows Phone apps

“RemObjects is using its experience with compilers to allow developers to use Apple’s Swift coding language for Android development,” Benjamin Mayo reports for 9to5Mac.

“Previously, the company did something similar for C# and now the company is tackling Swift,” Mayo reports. “Silver allows app makers to write in the Swift language (which is still in its infancy, really) but code against the API’s and frameworks of non-Apple platforms.”

Read more in the full article here.

Related articles:
Popularity of Apple’s Swift language expected to rise to even higher level in coming months – August 12, 2014
Why Apple’s Swift language will instantly remake computer programming – July 14, 2014
Apple’s new Swift blog signals just how vested Apple is in its new language – July 14, 2014
iOS, Mac coders liking what they see in Apple’s Swift programming language – June 23, 2014
First Impressions of Apple’s new Swift programming language – June 23, 2014
Apple publishes second free Swift code manual to iBooks Store – June 13, 2014
Swift: Who is Apple’s new programming language for? – June 12, 2014
Apple’s Swift programming language and what it means for developers and users – June 11, 2014
Apple’s Swift is instant hit among top programming languages – June 10, 2014
Swift: Apple’s next-gen programming language 4 years in the making – June 4, 2014
Why developers are going nuts over Apple’s new ‘Swift’ programming language – June 3, 2014
Apple just delivered a knockout blow to Android with iOS 8 – June 2, 2014
Xcode 6 features resizable device simulators, paving way for iPhones with new screen sizes – June 2, 2014
WWDC 2014: Apple sets the scene for its next decade – June 2, 2014
Apple unveils new versions of OS X and iOS, major iCloud update with iCloud Drive – June 2, 2014
Apple’S WWDC news bores investors, not developers – June 2, 2014
Apple’s HealthKit aims to unite wearables and fitness apps – June 2, 2014
Apple releases iOS 8 SDK with over 4,000 new APIs – June 2, 2014
Apple unveils iOS 8, the biggest release since the launch of the App Store – June 2, 2014
Apple announces OS X Yosemite for Macintosh – June 2, 2014


    1. WRONG! This is EXACTLY what Apple wanted to happen. They want developers to adopt swift. Most cross-platform development happens in a more expressive and easy to deal with language, like C#. Swift has enough C#-like features to make developers happy.

      Swift is a cool language, but they need stuff like this to become a major language. The easier you make it for devs to work in your native language, the better the apps are going to be for your platform.

      1. I don’t think so.

        Apple has always preferred to persuade developers to take advantage of the unique qualities their platform has (compared to the others). This was the reason for the fierce opposition to Flash. Their arguments are easy to digest: using all these cross-platform tools significantly diminishes the advantages of iOS (or Mac OS X) as a unified hardware/OS platform by limiting developers to the features only available on all platforms (i.e. lowest common denominator), which essentially brings down iOS / Mac OSX to the level of Android / Windows. Apple has always much preferred that their developers use Apple’s own tools (and they made it easy by simplifying porting their effort to all Apple hardware.

        1. You seem not understand critical parts of how app development works.

          All the Apple exclusive hardware and features are tied to Apple specific API’s (Cocoa on iOS), not the language (Swift, Objective C, or C on iOS).

          The language Swift, like C, is a general purpose language. No part of its design is tied to any specific platform. Developers using Swift on Android or Windows would still have to use same Android API or Windows API, instead of using the Apple specific API Cocoa.

          More developers learning Swift and adopting it on other platforms would in no way threaten Apple’s vertical integration model, and it would clearly be a good thing for Apple if the app developer community had more general knowledge and experience programming with Swift.

  1. Hope they’re only hoping to target CISC processors because… You know… You can’t take code written in one language and compile it both for CISC and RISC.


    1. As Alan Turing observed almost seven decades ago, any task that is performable on one general purpose computing device is performable on any other. That doesn’t mean it can be done as quickly, effectively, or efficiently. The NSA could do complex cryptography on a Raspberry Pi, but it would take centuries. Obviously, a program written in a processor-agnostic high level language can be compiled to run on either RISC or CISC processors, but that doesn’t mean it will run as well on both.

      On top of that, there are a lot of existing programs that aren’t really processor agnostic. A programmer who knows a trick to make his program run faster or better on a particular machine or compiler will usually play the trick, even if it makes the code less portable.

      Those factors (and others) mean that translating a program from iOS to Android or Intel to ARM is not just a matter of running the same Swift code through a compiler with a couple of flags reset.

  2. Awesome. Rem Objects makes some great compilers.

    Their C# and Object Pascal compilers are very well done.

    I like their approach to cross-platform and am looking forward to seeing what they come up with.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.