When you build your app for devices with iOS lower then version 8, NativeScript will use the static images and when you use NativeScript to build your app for devices with iOS 8 and above, it will use the provided LaunchScreen.storyboard. The default Hello-World project in NativeScript is provided with default settings that supports bothĪpproaches. In iOS 8 and above, the approach is to createĪ LaunchScreen.storyboard, which is much more powerful in terms of customization and is easier to maintain. Images, each with different resolution for each iOS device. The drawback of this method is that the app developer will have to provide many different In iOS 7 and lower, the approach for creating the launch screen is to use static image resources. Setting up launch screens depends on the version of iOS you are targeting. If on a real device: remove platforms folder from your project, delete app, restart device, redeploy. ![]() If you’re updating icons or launch screens and not seeing your changes, delete the application from your device or emulator and redeploy. WARNING: Occasionally, the iOS operating system caches your application’s icons and launch screens. In this article, we are going to introduce the workflow to create your own launch screens. In NativeScript, your application comes with predefined template settings and images for these steps. To be published successfully in the App Store, there are some requirements that need to be fulfilled.Īs described in iOS Human Interface Guidelines setting the following is mandatory: Publishing your iOS app is an essential step in the development process and in order for your iOS application Creating Launch Screen and AppIcons for iOSĬreating App Icons and Launch Screens for iOS.You can grab this from my code samples repo. I've put together a quick sample app, so you can see how this works in action. To set it back to the original, just pass nil for the icon name.Įnum AppIcon : String, CaseIterable // Which can be used like. The code to set an app icon is incredibly simple. Repeat this for your app icon with "AppIconThumb". ![]() ![]() You have to do this as once you ship the app via TestFlight, the image will not show via UIImage unless you search through your bundle to find the file ( and having one extra small file is a little easier ). Whilst you're in here, add an individual image ( not an App Icon ) called "AlternateIconThumb". ![]() In this case, i've just called it "AlternateIcon". Next, open up your asset catalogue and drag in a new app icon file, with a different name. If you're curious what this does, xcode will now add the needed keys and values to your plist for each app icon you provide, instead of you having to do it all manually. To get started open up your apps build settings, select all and combined, then search for "Asset Catalog Compiler - Options". Thanks to a change in Xcode 13, you can drop the plist and speed up adding new icons. The only problem is that it was really easy to mess up - lots of manually generated files and entries in a plist. Its gradually getting more common to see apps offering alternate icons, and its always been pretty easy to do.
0 Comments
Leave a Reply. |