Last week we announced the new .dev top-level domain (TLD) was open for Early Access registrations. As of today, .dev is available to anyone through your registrar of choice (typically $12-$15 for standard priced domains, varies by registrar).
We envision .dev as a home for developers. From tools to programming languages to blogs, .dev is the best place for all the amazing things that you build. Over the past few months, we've launched, or re-launched, many of our own developer sites on the new domain. Here are some of our favorites:
- Learn how to build a better web at web.dev.
- Start your open source journey with the right license. Did you know that without the right license, software isn't really open source? Opensource.dev explains why.
- Learn how to build beautiful native apps on iOS and Android from a single codebase. Visit flutter.dev to learn more.
- Join the TensorFlow community at tfhub.dev.
- Analyze and tune your software with performance tracing for Android, Linux, and Chrome. Check out perfetto.dev.
- Get your hands on Puppeteer, a Node library that provides a high-level API to control Chrome or Chromium over the DevTools Protocol. Get it at pptr.dev.
But we're not done yet! We've got big plans for .dev, and we'd like to invite you to join us. To start, everyone who applied for a ticket to Google I/O 2019 will get a .dev domain at no cost for one year. If you entered the drawing, check your inbox for your redemption code. We'll be moving more of our existing projects and launching some exciting things on .dev in the months to come. We can't wait to see what you build on .dev -- share what you create with #hellodotdev.
Unreal Engine 4.22 will be releasing soon with a number of fixes and updates. In the meantime, the first Preview is now available for download from the Epic Games launcher.
Preview 1 includes support for real-time ray tracing, Editor Utility Widgets, Movable Spotlight support on mobile, virtual production updates, and Blueprint indexing optimizations.
A full list of the upcoming changes to this build are available on the Unreal Engine forums. We invite you to provide feedback on Preview 1, and all subsequent releases. Please keep in mind that Preview releases are intended only to provide a sample of what is going to be released in the update and are not production-ready.
To get started with Unreal Engine 4.22 Preview 1, head to the Unreal Engine section on the launcher, select Library at the top, then click the plus icon next to Engine Versions and choose 4.22 Preview 1.
On Jan. 9, 2019, Google's new policy about certain SMS-related permissions will come into effect. The new restrictions will apply to the use of the RECEIVE_SMS permission that Facebook's Account Kit for Android uses in some cases.
If your app uses this optional permission, you can remove the RECEIVE_SMS permission from your app's manifest to comply with the new policy and ensure that Account Kit keeps functioning as expected. However, the verification code received via SMS will stop being populated automatically.
Developers can also file a permissions declaration form to avoid being removed from Google Play. Based on the Google informational page, developers need to submit the form by Jan. 9 and will have until March 9, 2019 to bring apps into compliance. Check out the Google website for more information about this change and ways to file for an extension.
Facebook is dedicated to serving its developer community, and given this new policy, the next version of the Account Kit SDK will no longer use the RECEIVE_SMS permission.
Hello Google Play Developer,
In our latest blog post, we detailed the requirement that apps using native code must provide a 64-bit version in addition to the 32-bit version by August 1, 2019. As you may know, 64-bit CPUs deliver faster, richer experiences, and we appreciate your support in ensuring our users have the best experience possible on the Android platform.
If you haven't yet, we encourage you to begin work for the 64-bit requirement as soon as possible. Many apps are written entirely in non-native code (e.g. the Java programming language or Kotlin) and will not need code changes.
Please note that we are not making changes to our policy on 32-bit support. Google Play will continue to deliver apps with 32-bit native code to 32-bit devices. The requirement means that those apps will need to have a 64-bit version as well.
To help you make the transition, we've prepared documentation on how to check whether your app already supports 64-bit and how to become 64-bit compliant.
We're also providing a high-level timeline below.
Starting August 1, 2019:
- All new apps and app updates are required to provide 64-bit versions of any 32-bit native code they provide.
- Extension: Google Play will continue to accept 32-bit only updates to existing games that use Unity 5.6 or older until August 2021.
Starting August 1, 2021:
- Google Play will stop serving apps without 64-bit versions on 64-bit capable devices, meaning they will no longer be available in the Play Store on those devices.
- This will include games built with Unity 5.6 or older.
The requirement does not apply to:
- APKs or app bundles explicitly targeting Wear OS or Android TV, which are form factors that do not currently support 64-bit code.
- APKs or app bundles that Google Play won't install on Android 9 Pie or later (support for 64-bit does not need to extend to APKs that are only on Android 8 Oreo and below).
If you have any questions, you can find additional information about adding 64-bit support here.