The authors of React use the phrase “learn once, write anywhere”. With React and React Native, your web app can share most its logic with your iOS and Android apps, but the view layer needs to be implemented separately for each platform. We have taken this a step further and developed a thin cross-platform layer we call ReactXP. If you write your app to this abstraction, you can share your view definitions, styles and animations across multiple target platforms. Of course, you can still provide platform-specific UI variants, but this can be done selectively where desired.

ReactXP is designed with cross-platform development in mind. In general, it exposes APIs, components, props, styles and animation parameters that are implemented in a consistent way across React JS (HTML) and React Native for iOS and Android. A few platform-specific props and style attributes have been exposed, but we have tried to keep these to a minimum.

Without diving into the app, we can use storybook to quickly render "dumb" components that don't manage any state internally with mock props. By leveraging the same tooling, we can quickly follow the web team who originally adopted storybook. Along with hot reloading, storybook dramatically accelerates our UI development cycle. Our designers can even easily tweak styling directly in storybook.

It was painful and time consuming to upgrade our React Native fork which fixes issues specific to our use cases. Nowadays, releases are more stable. Compared to spending days before, it only took us few hours to upgrade our fork to 0.55 from 0.53 recently.

Apple UI Design Resources for iOS include Sketch, Photoshop, and Adobe XD templates, along with comprehensive UI resources that depict the full range of controls, views, and glyphs available to developers using the iOS SDK. These resources help you design apps that match the iOS design language. Icon and glyph production files are preconfigured to automate asset production using Sketch slices or Adobe Generator for Photoshop CC. Color swatches, dynamic type tables, and fonts are also included.

One of the most significant design opportunities in recent history was announced with a simple blog post on Apple’s website. “Let me just say it: We want native third-party applications on the iPhone, and we plan to have an SDK in developers’ hands in February,” Steve Jobs wrote. On a quiet Thursday morning less than a year later, the App Store opened to iPhone users with a selection of just over 500 apps.

Samsung Gear 360

Few contemporary innovations have changed how we live our lives and interact with the world around us more than iPhone apps. The creators of the first 500 available at launch had the unique opportunity of shaping the design direction and interaction methods of the millions of apps created since.

You need 4 things to make a PWA: HTTPS hosting, a service worker, a properly configured index.html file, and a web app manifest.json file. The examples below are geared towards React but are similar for any framework.

A challenge in configuring your app is understanding the difference in how iOS and Android use the meta tags in index.html and the web app manifest. We’ll explain how each option is used below.

One painful part to this process is creating the massive number of splash screens for iOS: one for each screen size and orientation you want to support, otherwise users will see a white screen while your app loads.

One of the most common questions I receive from beginning UI designers is: what font size should I use for my project? Sometimes they’re asking about a website, sometimes an Android app, sometimes iPhone/iPad. And you know? I empathize. Material Design has nice guidelines, but they’re like 50 pages long. iOS… well, they don’t even have nice guidelines! And the web is (still) the wild west. Maybe some article pops up – whoa, new sheriff in town – and tells you what font sizes to use based on some dark magic involving the golden ratio, but

With iOS 11.3, Apple has silently added support for the basic set of new technologies behind the idea of “Progressive Web Apps” (PWAs). It’s time to see how they work, what are their abilities and challenges, and what do you need to know if you already have a published PWA.

If you came here and you still don’t know what a PWA is, let’s start saying there is no unique or precise definition. But it’s an app created with Web technologies that −without packaging or signing− can work offline and can optionally be installed in the operating system where it will look and act like any other app.

There is no App Store process involved in most platforms−only Edge/Windows 10 is currently forcing PWAs to be in the store.

So an iOS user might end with four or more copies of the same PWA per device (I’m talking about the service worker and files cached by it, not the icon).

When there is a manifest linked in your HTML, Safari will use it instead of the old non-standard apple-mobile-* meta tags. That’s great! However, as far as of beta 1, you might also have some unexpected behaviors compared with Android.

Let’s start talking about which properties are ignored (but it’s beta 1, I don’t know which features will get there and which properties not):

I recently wrote an article called “Native Apps are Doomed.” I was surprised at how many people were defending native apps. In all honesty, the user experience story for native apps has never been impressive. The numbers paint a bleak picture for native app success rates that teams need to be aware of when they make important decisions about how to build a new app.

The templates are part of NativeScript Sidekick, a GUI client companion to the NativeScript command-line interface. Sidekick was introduced on Tuesday. Along with the templates, Sidekick contains plugins, cloud builds, and debugging support. Progress Software, the developer of NativeScript, offers Sidekick as a free download.

Featuring a set of cross-platform abstractions and runtimes, open source NativeScript allows you to develop native mobile apps with JavaScript, TypeScript, or Angular. A NativeScript runtime translates between JavaScript, TypeScript, and Angular and the native APIs on Apple iOS and Google Android, allowing developers to write an application just once to support both platforms.

Earlier this year we published a demo app showcasing our port of Node.js with ChakraCore to iOS. In the accompanying blog article, we talked about how Node-ChakraCore opened a unique opportunity for Node.js to work on iOS, and consequently a path for Node.js to become a viable building block for mobile applications.

The engineering team at Janea Systems has continued to work hard and passionately on this project; so today, we are excited to announce the first alpha release of Node.js for Mobile Apps: a toolkit that enables developers to harvest the power of Node.js and its module ecosystem in their mobile applications. At the heart of it, is a library – available for Android and iOS – that allows an app to host a full-fledged Node.js execution environment. In addition to the core library, we have released plugins for Cordova and React Native – both also compatible with Android and iOS – which make it extremely easy to integrate the Node.js runtime into applications built using on those frameworks.

React Native allows you to build mobile apps by using only JavaScript. It is based on ReactJS and uses the same design. React Native enables using the React architecture as native application on Android, iOS, and Windows applications. Using React Native, you can compose a rich mobile UI from React components. React Native was announced by Facebook in 2015. React Native apps are indistinguishable from native apps built using Objective-C or Java. React Native has seen a steady rise in usage. The demand for React Native apps and developers who can make React Native apps has only gone up. React Native developers can make high salaries and get great jobs all around the world. As React Native is primarily based on ReactJS, if you have any knowledge of React you already have a head start on React Native development. Here’s some of the very best React Native books, videos, courses, and tutorials to help you learn React Native in 2017.

Most travellers make last-minute decisions, even though they spend significant time researching things to do before embarking on their trip. Finding a hotel and flight is relatively easy, but when it comes to tours and activities, the problem is that late or last-minute bookings are not always available, and if they are, the process of making a purchase online is often hard. The mobile experience can also be limited because many websites are slow or their booking process is long and complex.

In this article, we’ll present a case study and share observations on the project we designed and built,

Apple this week began work toward integrating Service Workers, an API that lets browsers run background scripts, into WebKit, suggesting the company might one day support a form of next-generation web app in iOS.

Apple quietly revealed work on the technology in an update to its WebKit Feature Status webpage this week, which now shows Service Workers as "In Development," reports The Register.

As noted by Fortune, which also reported on the change, Service Workers comprise part of a larger Google-backed

I recently wrote an article called “Native Apps are Doomed.” I was surprised at how many people were defending native apps. In all honesty, the user experience story for native apps has never been impressive. The numbers paint a bleak picture for native app success rates that teams need to be aware of when they make important decisions about how to build a new app.

Apple’s Worldwide Developer Conference (WWDC) has been running for 34 years, which is 6 years longer than The Simpsons. Like Netflix, Apple likes to drop a whole season at once. When it does, I devote that week and the following weekend to binge-watching as many videos as I can and trying out some of the new technology, especially as it relates to iOS.

In the past 10 years, a big portion of these conferences has been devoted to iOS. This is where we learned about the first iPhone SDK, notifications, share and today widgets, the iOS 7 redesign, iPad multitasking, and other iOS milestones. I was genuinely surprised with some of the announcements this year.

Over the last 6 months, I’ve been building Rizer, a mobile app that allows users to judge photo battles from multiple categories (currently Animals, Babies, Food, Funny, Men, Nature, and Women) as well as submit their own photos to these categories to be judged. Photos are ranked using the ELO algorithm (what Eduardo Saverin drew on the window during that awesome FaceMash scene in The Social Network), with the highest rated being displayed on Rizer’s Leaderboard.

Rizer is a Hybrid app that uses Apache Cordova and its plethora of native plugins to gain access to important native functionality on the user’s device such as: receiving push notifications, taking pictures with the camera, and processing in-app purchases.

Native apps are built in native programming languages like Objective-C or Swift for iOS and Java for Android operating systems. Hybrid apps are mobile apps built using HTML/CSS/JS “pages” wrapped in Phonegap/Cordova.

Hybrid apps need to be written once and can be built for both Android and iOS (and Windows Phone…). This saves development time that in turn saves development cost. With any software come bugs. While there will be similar bugs in android and iOS for hybrid apps — there will be two different types of bugs in native apps since they’re built off of two different code bases.

Rapid prototyping is possible by building on top of existing themes and functionality For eg.

This is what I see in Chrome when canceling a Promise. In Safari, you see a dash and no bytes transferred. Same effect.

What we found was that unsubscribing from an event stream in Rx did a very crucial thing: it meant nothing was “listening” to the data stream after the subscription was canceled. What it didn’t do: stop the browser from resolving the Promise.

Under the hood, we use Axios for promises. It’s proven to be an awesome library, with regular development as it moves toward v1.0. We found that the best way for us to implement it in a complex application was to abstract away the implementation details and give developers a simple

This list was last updated January 2017. Dates and locations are subject to change. If you have recommendations for conferences to add to the list, leave them in the comment section below! We’ll be continually adding conferences to the list.

Now that 2017 is really in swing and spring is on its way, maybe you’re thinking about renewing your job search. At Stack Overflow, we have our finger on the pulse of the developer hiring scene, and we’ve put together some data on 2017 hiring trends to help you steer your search.

These are some of the trends we’ve seen in job posting and employer activity leading into 2017.

Changes in Demand

We looked at targeting options for employers on Stack Overflow Jobs that were used by at least 200 companies since the beginning of 2015. The fastest growing targets are ReactJS, Docker, Ansible, and Apache Spark, followed by System Administration and QA.

In this article I will introduce you to a project with I have developed over the last few months. It aims to share as much code possible between Android, iOS, Web and Desktop, but tries to look and act like a first class citizen.

At first, I start with a short introduction where I come from and then I will present you the project in detail. Feel free to ask me anything in the comments :) and enjoy the read.

It is the dream of every developer. Write your code once and run it on every device possible. This would result in less development time and costs, fewer bugs and a broader audience.