haawe.blogg.se

Here’s the image I used for Pokémon Types, as an example. png image asset that represents your app.

To get your production-ready app icon files in place, you need to first create a 1024 x 1024 pixel. The NativeScript placeholder icon on the home screen of an iOS device When you start a new NativeScript app you get a placeholder icon, which is fine for development, but for production you need to replace the placeholder icon with the image you’ll want to go to the stores with. Your app’s icon is the first thing you users notice about your app. You can now use the NativeScript CLI’s tns resources generate icons to generate your app icons from a single source image. UPDATE: Since this article was first written we’ve automated this step. TIP: If you’re finding the steps in this article overwhelming, you might want to consider building NativeScript apps in NativeScript Sidekick, which has tooling to automate many of this article’s workflows.

When you’re ready, grab some coffee, and let’s get started!

In fact, to give this article a bit of real-world context, I’ll be using a simple app I recently deployed to the stores, Pokémon Types, to give concrete examples of the things you need to do to make your next app a reality. If you’ve never published an app to the stores, you should set aside at least two full days-yes, days-to complete the monotonous processes that this article spells out.ĭon’t worry though once you’ve completed these steps once, it’s a whole lot easier to go through the process in the future, and I’ll be sharing a handful of tips & tricks as we work through these steps. Publishing an app to the stores is hard-there’s no point sugarcoating that. This article is a straight-to-the-point checklist for deploying a NativeScript-built app to the iOS App Store and Google Play.