Category: Android

I have been an Android user since the G1 and primarily focused on building and using PCs. While I have never really engaged with Apple products, my interest in technology has kept me aware of their developments.

I owned a couple of iPods in the past, but after a mishap with iTunes that messed up my music library, I decided to distance myself from Apple products for a long time. Recently, I began pondering a question that many in the tech community might relate to: For those who have been loyal Android users for an extensive period, what has your experience been in switching to an iPhone?

I am curious to know what motivated you to make that transition and what your impressions were post-switch. Did you find it difficult to adapt to the iOS environment after being accustomed to Android?

Or did certain features and functionalities sway you towards embracing an iPhone? I’m interested in hearing about both the challenges and the benefits of making such a switch.

Ultimately, it’s fascinating to consider how individuals weigh the pros and cons of moving from one platform to another, especially after investing years in a particular ecosystem. So if you’re someone who has made this leap, I would love to hear your insights and experiences regarding that change.

Your perspectives could shed valuable light on the appeal of Apple’s offerings as compared to the flexibility of Android.

Apple’s Swift programming language is now officially being extended to support Android app development with the creation of a dedicated Android Working Group within the Swift open-source project. This marks a significant evolution for Swift, which was initially introduced by Apple in 2014 as a modern language intended for iOS, macOS, watchOS, and tvOS.

Since then, Swift expanded to support Linux and Windows, and now it aims to include Android as well. The announcement from the Swift project details a structured approach to incorporating Android into Swift’s ecosystem.

The Android Working Group’s charter outlines specific responsibilities that include enabling Swift to be compiled and executed on Android without relying on unofficial modifications, enhancing its standard libraries for better compatibility with Android APIs, and developing native tools and workflows for developers targeting Android applications with Swift. Previously, developing Android applications in Swift relied on third-party solutions like the Scade framework or custom toolchains crafted by individual developers.

These methods often necessitated extensive configuration, lacked comprehensive support for Android APIs, and involved maintenance challenges due to inconsistencies with Swift updates. A primary objective of the new working group will be to improve official support for Android within the Swift distribution.

This includes eliminating the dependence on out-of-tree patches or community-maintained forks and ensuring compatibility with other officially supported platforms. The group also plans to recommend enhancements to core Swift libraries, such as Foundation and Dispatch, to align them more closely with Android’s conventions and behaviors.

Currently, Kotlin remains the dominant language for Android app development, having been designated as Google’s preferred language since 2017. The advancements in Swift’s support for Android could introduce new dynamics into the mobile development landscape.

The Android Workgroup is dedicated to promoting the adoption of Swift for Android application development. Its primary objective is to facilitate the integration and support of Android as an officially recognized platform within the Swift programming language. To achieve this goal, the workgroup focuses on several key initiatives. These include enhancing and maintaining Android support for the official Swift distribution, thereby eliminating the reliance on out-of-tree or modified patches.

The workgroup also aims to improve core Swift packages, such as Foundation and Dispatch, to better align with Android’s conventions. Additionally, the group collaborates with the Platform Steering Group to formally establish platform support levels and work towards achieving designated support for Android. They are involved in assessing the range of supported Android API levels and architectures for seamless Swift integration. Another vital aspect is the development of continuous integration processes that incorporate Android testing within the Swift project’s pull request checks.

The workgroup identifies best practices for bridging Swift with Android’s Java SDK and packaging Swift libraries for Android apps. Support for debugging Swift applications on Android is also a priority, alongside advising and assisting in Android compatibility with various community Swift packages. For communication, the workgroup utilizes the Swift Android forum for discussions and can be privately contacted through direct messaging on the Swift Forums. Membership is open to anyone willing to contribute, and active discussions are facilitated through regular video calls and forum interactions.

Community members interested in joining can reach out to current members or request inclusion in the Android workgroup. Meetings are held biweekly on Wednesdays at noon ET, welcoming all Swift community members to attend and participate. Contributions to the workgroup’s initiatives can take various forms, including design discussions, question-and-answer sessions, bug reporting, tool development, and providing feedback directly to workgroup members.

Before watching WWDC, I was considering getting the One Plus tablet. However, after experiencing the upcoming features in iPad OS 26, I realized it wouldn’t be worthwhile to trade my iPad Pro for the One Plus model.

There’s no denying that the One Plus tablet offers great value, priced at $700 for a 13-inch device with impressive specs—and it even includes a free keyboard at the moment. This makes it a solid contender compared to the $1,200 iPad Pro.

In fact, when compared to the 13-inch iPad Air, which costs around $800, the One Plus tablet doesn’t really seem like a direct competitor. One significant drawback is the absence of an OLED display, which feels like a step down if you’re accustomed to the newer iPad Pro.

Another considerable advantage of the iPad is the app ecosystem. While iPads don’t have as many apps as the iPhone, there is still a substantial difference when compared to Android.

The concern about whether an iPad can replace a computer is becoming less relevant due to the advancements in iPad OS 26. Features like improved multitasking, file management, and audio input handling have made significant progress.

Many users of MacBook Airs would likely find that a modern iPad meets their day-to-day needs without any major issues. However, power users needing specific Mac or PC software will still find it hard to make the switch.

There’s room for improvement, but I’m genuinely excited about the latest changes in iPad OS. If Apple could lower prices a bit (though I know that’s unlikely), it would make the iPad even more appealing.

With the release of iOS 26, Apple has introduced a new feature that enables users to transfer eSIMs between iPhones and Android devices. This update simplifies the process of moving phone numbers across platforms, eliminating the need for users to reach out to their carriers for assistance during the transition. Some users have already discovered a “Transfer to Android” option within their cellular settings, although it is important to note that this feature is not available for all service plans at the moment. An example includes an iPhone user utilizing US Mobile’s Dark Star eSIM, who was able to find the transfer option.

When adding an eSIM in iOS 26, there is also a corresponding “Transfer From Android” feature. By selecting this option, users can generate a QR code that can be scanned using an Android device to initiate the transfer. The transfer process works both ways, allowing seamless movement of eSIMs between devices. It seems that Apple rolled out this functionality in collaboration with Google.

Prior to the launch of iOS 26, an Android 16 beta hinted at the development of cross-platform transfer capabilities, paving the way for this innovation. In earlier versions, such as iOS 18, transferring an eSIM from one iPhone to another was straightforward. However, moving an eSIM from an iPhone to an Android device proved to be a much more cumbersome task, often requiring users to obtain a QR code from their carriers. With the arrival of iOS 26, the transition process for many iPhone users switching to Android should become significantly more manageable.

Apple’s upcoming iOS 19 update is expected to simplify the process of transferring an eSIM from an iPhone to an Android smartphone. According to a report from Android Authority, a new “Transfer to Android” feature has been discovered in the beta version of Google’s SIM Manager, indicating that users may soon have a wireless option for such transfers. Currently, transferring an eSIM from an iPhone to another iPhone is straightforward.

However, the process becomes complicated when switching to an Android device, typically requiring users to contact their carrier for assistance. The new feature could change this, allowing for a more seamless transition between the two types of devices. It is speculated that the “Transfer to Android” option will be integrated into the existing “Transfer or Reset iPhone” interface found within the General section of the Settings app.

Apple may also enhance its eSIM Quick Transfer capability, which currently facilitates transfers between iPhones, to include Android devices. Additionally, a QR code backup feature may be provided in case a wireless connection fails. The code found in Google’s SIM Manager indicates that the transfer functionality will rely on iOS 19, implying that this feature will be unavailable on earlier versions of Apple’s operating system.

To initiate the transfer, users will navigate to the Settings app, select General, and then choose “Transfer or Reset iPhone” before following the prompts for transferring to Android. While we may learn more about this feature at the upcoming WWDC, it could also be introduced quietly. Furthermore, Google may be developing a reciprocal feature to facilitate transfers from Android to iPhone users.