Elm Native UI

Experimental support for writing native iOS and Android applications in the beautiful functional Elm language. This project builds on Facebook's React Native, using it as the JavaScript environment for Elm.

Frequently Asked Questions

Is This Production Ready?

No. This is really just an experiment, and it is not under active development. People have used it for applications despite this.

Why React Native?

Mobile applications are expected to look and feel at home on the device and the OS it is running. This goal cannot really be achieved with a WebView-based solution (such as Cordova). React Native applications use the same pieces of UI as an app built with Objective-C or Java, choosing the platform-specific native variant of the UI feature for you.

Will it always be React Native?

In the long term, not necessarily. The ultimate goal would be for Elm Native UI to be a standalone project, complete with the mobile platform groundwork that has been put into React Native already. It has not been fully assessed how much work this would in reality entail.

Addendum 2017-10-17: elm-ios was a Google Summer of Code project that explored this idea for iOS.

Get it running

Caution: Experimental software!

Elm Native UI may get breaking changes at any time, and it might only work with an older version of React Native.

Actually getting it running

Install React Native following their guide. Check that you can create a new project:

$ react-native init MyAppName --version 0.44.3

and try running it on a real or virtual device.

Once that works, clone this repository in the same directory where you ran react-native init in. You should have a directory structure similar to this:

│
├── elm-native-ui
└── MyAppName

Go ahead and copy the files from the examples/Counter folder into your React Native app directory now.

Now try to compile the Elm code with

$ npm run compile

This will create the elm-package.json and elm-stuff for you, even though it won't compile yet.

Edit the index.*.js files' last lines in case your React Native app is not called 'MyAppName' at this point. You may also need to rename the project in the package.json file.

You can then use e.g. elm_self_publish to publish the Elm Native UI package into our project.

Assuming we're in the parent directory where elm-native-ui reside:

$ python path/to/elm_self_publish.py ./elm-native-ui ./MyAppName

Now we are ready to rock! 🤘🎸

Just to list out the basics:

# install dependencies
$ npm install
# compile Elm with
$ npm run compile
# run app on iOS
$ react-native run-ios
# or run on Android
$ react-native run-android

When you make changes to the code, you only need to recompile Elm and press Cmd-R on the Simulator (iOS) or refresh the emulator (Android).

If you wish, you can also start a file watcher for *.elm files, which will recompile whenever you make a change:

$ npm start

React native versions

If you use the package.json files from the example projects, you'll get the react native version that has been tested and known to be working with the examples.

That is currently react-native 0.44.3

Later versions of react native may work, however, specifically in the subsequent react native 0.45.x release the "Navigation Experimental" module was depricated and moved to an external library, so the Navigation Example will not work. The intention is to port this to "React Navigation", which is now the accepted approach for react apps. The counter app still works, so if you don't use navigation your app should work with more recent versions.

How it works

This section was outdated, but for an overview of the older structure, read this blog post: Elm Native UI: Writing a React Native app in Elm

You can also watch this ElmCast Live episode, where @ohanhi explains some of the differences between the old and the new versions. (You can safely skip the first 5 minutes, as we had technical issues in the beginning.)

Screenshots

iOS	Android

To Do

• Basic PoC
  • Show something from Elm
  • Make basic VTree work
  • Add some kind of event handlers
• Library
  • Make main support our VTree (see this suggestion)
• Styles
  • Basic types for styles
  • Support object type styles - transform styles and shadowOffset
  • Make enum type styles safer
  • Allow the StyleSheet.create method for styles
• Props
  • Improved event handlers
  • Support props besides styles and event handlers
  • Unify syntax for styles, handlers and other props
• Core features
  • Navigation (NavigationExperimental)
  • Tasks (HTTP calls, storage)
  • UIExplorer / Component examples

License

BSD (3-clause)