Does this support iPad and Android tablets? How about Windows tablet support?
We don't support Windows Phone - just iOS and Android.
Android tablets should work. We don't have native iPad support but we're planning on adding it.
Exponent – Build native apps in JS that work across both iOS and Android
61–70 of 119 posts
Re: Exponent – Build native apps in JS that work across both iOS and Android
#62Without support for native modules, is it at all possible to use something like card.io with Exponent? Also, are there any plans to allow plugins that make use of native modules in the way the core SDK uses them?
card.io isn't supported right now, but it's definitely on our list! If you want to use it right now you can send us a PR or just maintain a fork of our clients.
We have some plans to allow custom native modules without forking the client but that's probably a few months out. If you join our slack we'll let you know about any updates: https://slack.exponentjs.com/
Re: Exponent – Build native apps in JS that work across both iOS and Android
#63Does it allow recording video from the camera?
We support taking images with the camera but no video yet: https://docs.getexponent.com/versions/latest/sdk/imagepicker....
Re: Exponent – Build native apps in JS that work across both iOS and Android
#64Re: Exponent – Build native apps in JS that work across both iOS and Android
#65Earlier quoted context omitted.
We don't support Windows Phone - just iOS and Android. Android tablets should work. We don't have native iPad support but we're planning on adding it.
I'm talking about Windows tablet , not Windows phone.
Ah sorry, misread your comment. The dev tools will run on Windows 10, but the client apps won't. The client apps run on iOS and Android and the dev tools run on macOS, Windows, and Linux.
Re: Exponent – Build native apps in JS that work across both iOS and Android
#66Re: Exponent – Build native apps in JS that work across both iOS and Android
#67The video says you support Linux for XDE but I don't see[1] a build for it. [1] https://docs.getexponent.com/versions/v10.0.0/introduction/i...
For Linux, you have to build it from source. https://github.com/exponentjs/xde#build-from-source It's usually pretty smooth to do so.
I think it would make sense to provide pre-build packages for few popular distros (Ubuntu, CentOS, Arch). There are some tools that make it much easier, i.e. fpm (https://github.com/jordansissel/fpm).
Re: Exponent – Build native apps in JS that work across both iOS and Android
#68I've been building React Native apps since the platform was released. Exponent not only makes the process much easier and approachable, it makes it a breeze to share the final app with your clients or people who you want to test externally. The team at Exponent also contributes a ton to the RN ecosystem as core contributors to React Native and open sourcing a lot of awesome RN components. If you're looking at building cross platform mobile apps I highly recommend checking out Exponent!
Re: Exponent – Build native apps in JS that work across both iOS and Android
#69Earlier quoted context omitted.
For Linux, you have to build it from source. https://github.com/exponentjs/xde#build-from-source It's usually pretty smooth to do so.
I think it would make sense to provide pre-build packages for few popular distros (Ubuntu, CentOS, Arch). There are some tools that make it much easier, i.e. fpm ( https://github.com/jordansissel/fpm ).
We're planning on doing an AppImage for Linux since we're using Electron Builder (https://github.com/electron-userland/electron-builder). Just haven't had time for it yet!
Re: Exponent – Build native apps in JS that work across both iOS and Android
#70I tested out React Native on Android the other day and it was a real disaster. It doesn't compile for all the CPU ABIs (instruction sets) we have, so if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely. You have to remove all your own libraries for unsupported architectures, then modify your build not to include them, then depend on those platform's compatibility features to run React Native's libraries built for older ABIs like arm v7.
Once you get it running despite their poor support for Android CPUs in their native libraries, half the examples and half the dependencies on the web out there crash immediately because they decided you have to import React and Component from "react" instead of "react-native" now. And there's no stack trace at all when it crashes for that error since it crashes before the normal source map functionality that provides them. My company has hundreds of files being used by React Native on iOS, but they are unusable due to this, even hours of search and replace cannot fix it because it is still crashing out, probably due to one of a dozen dependencies. Similarly if you try to use react redux 4 you are screwed, only 3 is supported. Woe be to anyone who upgrades that dependency.
As a Java programmer who is used to compile time errors when something is wrong, React Native where it crashes constantly at runtime due to poor platform decisions like forcing developers to use a different package from earlier versions is a tough pill to swallow.