iPhone 13 Pro/iOS Impressions from a Pixel 3/Android User

Last week on Wednesday my new Apple iPhone 13 Pro finally came in. I was super excited to get it all unboxed, SIM card inserted (I put my case on and then realized I needed to put the SIM card in, then had to take the case off again :facepalm:) and then put the case back on, ready to use as my next phone for the future (or until Apple no longer supports the device). Below are some of my initial and first impressions from someone who has only used an Android phone consistently in the past and is using an iOS device for the very first time as their main mobile phone.

Look and Feel

The Apple iPhone 13 Pro is built like a tank when compared to my old Pixel 3 phone. It is very close in size, with the iPhone 13 Pro being only slightly taller, wider and thicker but it is significantly heavier. I think the combination of the battery, stainless steel frame, and front and back glass make up most of that weight. When I pick up my old Pixel 3 it is like picking up a feather compared to picking up my iPhone 13 Pro. It took me a little bit to get used to the new weight difference. I do like this weight change though as it does feel a little more premium.

I like the way the phone does feel in my hand too. It is not too large and manageablefor single hand use, which is one of the reasons why I moved from Android to iOS. I am sorry Google but the Pixel 6 Pro to me does not look good, I absolutely hate the curved display on the edges and being such a large size makes it a deal breaker for me. The case helps to ensure that the frame does not dig into my hand and slightly protect my back cameras as there is a little lip.

One thing that I do know about Apple products is that generally they make extremely well-built products, be it their laptops to their tablets. Sure, sometimes they make “foldable” devices but by and large Apple does not skimp on using quality materials for their products. Paying for more premium products to get a better finished product is a no brainer for me and is something I am willing to pony up for. This may not be possible for everyone, but I am in a fortunate position where I can do this, so I took advantage of it.

I am a little disappointed in that it has a lightning port to charge the iPhone 13 Pro and I cannot use my many USB-3 cables that I have laying around, but it is what it is. The silent switch on the left-hand side of the phone is superb and I wish more phones incorporated something like this as it is very useful. The massive camera bump is not an issue for me, and I am not too fussed about the notch compared to other people. A single hole punch camera hole is a little cleaner but you lose out on Face ID.

iOS 15

Moving from Android to iOS I knew was going to be a little difficult at the start but there are a number of frustations that I have with iOS when compared to Android.

Less customization is something I knew I was going to lose on iOS. I did generally keep my Pixel 3 stock with what came out of the box, but I did like the ability to change the icon shapes, folder shapes and the ability to keep the icons, folders and widgets at the bottom of my screen and not have them all go at the top. That is my first gripe with iOS. Why does Apple not allow me to have icons, folders and widgets placed anywhere on my screens? I would like to have even easier access to my apps and folders by only using my thumb.

Something I thought I would not get frustrated by was notifications. Now I have to perhaps make some more changes in the settings, but I find notifications are absolutely horrible on iOS compared to Android. I find I am missing more notifications on iOS compared to Android. The notification center is okay but not great. I would like to have a small notification indicator on the top bar to know that “hey you have a message, etc.” instead of looking at the notification center. I am not too sure if it is a bug but there are times when I would get a message and sometimes I would get a notification sound and other times I would not.

I do like the iOS settings, permissions and app management compared to Android. Everything is more clearly laid out and is much easier to manage. Pulling down the control center from the right-hand side is also nice to have, but I found the universal pull down anywhere at the top on Android (notification drawer) to get access to quick settings and notifications is a little easier and more user friendly than how iOS makes you swipe down elsewhere for the notification center. If iOS could adopt something like this then that would be great.

My biggest two gripes are to do with notification/media volume levels and universal back gesture behavior on iOS. On Android you have dedicated alarm, notification/caller/alert and media volume controls while on iOS I found that managing my audio levels a major pain. I have no idea how I can keep my notification/alert levels high while keeping my media volume levels low. If I use the buttons on the side and keep the volume low all my sound minus the caller audio is low, and if I raise it then when I watch YouTube or listen to music, I need to quickly lower the volume. Perhaps I am missing something or have not set something up correctly but why are those volume levels paired? I would like to have all my notifications and alerts at the same level as my caller volume levels but keep my media volume levels low.

Now to the back gesture. This is something that I need to get used to as on Android I would swipe left from the right edge to go back to whatever screen I was on and even to previous apps sometimes. On iOS 15 there is no universal back gesture itself. You can go back to the main home screen by swiping up from the bottom or you need to press the dedicated back button located somewhere on the app which can be either on the top left or the bottom. It would be great to have a single and universal way to go back to the previous screen from any part of the right edge, but I guess that would fundamentally change the way iOS would work and would require apps to be re-worked to allow for the gesture.

All in all, I am not finding iOS very difficult to get used to. I am using many of the native Apple apps instead of my usual Gmail, Google calendar, Gboard apps, etc. But I do have installed Google Chrome and Google Maps as I have all my favourites, etc set up there and it would be a pain to migrate all of these to Safari or Apple Maps (as well as this being my only Apple device at the moment for personal use). All the other apps that I had used for travel, fitness, my smart home are all there so I have not lost anything but I did need to buy new licenses for the iOS app versions which is a little bit annoying but expected.

Final Thoughts

I knew there was going to be some initial teething issues with using iOS. I knew I had to adjust to the way iOS worked compared to Android. I knew that moving from a Pixel to an iPhone was going to require a little bit of mental and physical gymnastics. Overall though I did not find the initial migration and adoption of an iPhone or iOS that difficult. I do miss the ability to perform some customizations, the more accessible notifications and universal gestures. However I gain some of iOS’s handy streamlined, accessible and user friendly features while being housed in what I would again call a mobile tank.

Now I do have an iPad Mini 2021 version coming my way as well so that I can take more notes, read a little more and also watch videos and surf the web a little easier. Plus the new Apple Watch series 7 is also being delivered sometime next month. Did I jump completely in the Apple ecosystem? Yeah. For me to take advantage of everything that Apple offers I need to really start looking at investing in their ecosystem, even if it is for the next 5 years and has a very very steep entry cost. But I feel that in those 5 years (at least) it may be all worth it and I may be a permantely converted Apple user for mobile, tablet, watch (and perhaps laptop).

Bye bye Android and hello iOS

I wrote a blog post recently about potentially switching to the Apple ecosystem for my smartphone, smartwatch and tablet with the laptop also being an option. And I can officially say that I have bought an Apple iPhone 13 Pro, Apple iPad Mini 2021, and am waiting on the new Apple Watch 7.

If Apple do have an October 2021 event and showcase a new Apple Macbook Pro 14” with the M1X or M2 and it can support 32GB of RAM, 2 external monitors and have a good battery life then I may skip out on the Framework laptop and just go with the Macbook Pro. Even though I really like the repairability and upgradability of the Framework laptop there is no information about availability in Australia and my Surface Book 2 battery is not doing so great 😦

The more I see what the Pixel 6 Pro looks like the more I do not want it. The glossy back, the large size and the curved glass edges are all turn offs for me. I like to have a nice small smartphone that is powerful in the hands, and at 6.1” the iPhone 13 Pro is just that. Android 12 looks fantastic and what Google is doing with their software apps and assistant is going to be a major loss IMO by switching to iOS as that native support is gone. Most if not all the Google apps I use are on iOS so I am not missing too much there as Google seem to update their apps fairly frequently, sometimes even before they update their Android apps.

Currently I am still waiting for Apple to deliver my iPhone 13 Pro and Apple iPad Mini 2021, but I do have with me an Apple Pencil Gen 2 and leather case for my smartphone. The smart cover for the iPad Mini 2021 is still in transit the last I checked.

So by the end of October 2021, I will have my new smartphone and tablet, and am looking forward to using them. From the people that I have spoken to, getting used to iOS is not that hard and some of the workflow might make things a little easier. Overall I am looking forward to moving to a new mobile OS as I have been with Android for a very long time with a short stint using Microsoft’s mobile OS.

Will I go back to Android? Perhaps, but if I am happy using Apple’s products and they continue to support it for a long period of time (which from what I read and see, they like to continue to update their older devices) I may be in the Apple mobile ecosystem for a long time. My smart home/devices however will be still primarily Google/Nest and Philips Hue as I really like the Hubs and smart lights.

Thank you Android for all the fond memories starting with my HTC Desire HD all the way to my current Pixel 3. You have generally been very rock solid but the current hardware missteps, the lack of a proper first party smartwatch and tablet, and the poor security and update policy for the devices has made me decide to move on. I may see you again in the future :wave-bye:

React Native: NodeJS and Expo Start Failure

Recently I was looking at doing some React Native work so that I can quickly get some Android and iOS prototypes up and running to help me build the app that I actually want to get onto the Apple App Store and the Google Play Store.

To help me get a better understanding of what I need, I looked at several YouTube videos. The tutorials/guides were extremely useful, however I encountered an issue that was not present in the videos. When I ran the following command on my computer:

npm start

instead of the Expo DevTools running locally in my browser until I force killed it through Command Prompt, it would crash immediately and my Command Prompt would display an Unterminated Character Class error like below:

C:\Development\Android\React Native\Tutorials\rn-first-app>npm start

> @ start C:\Development\Android\React Native\Tutorials\rn-first-app
> expo start

Starting project at C:\Development\Android\React Native\Tutorials\rn-first-app
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Invalid regular expression: /(.*\\__fixtures__\\.*|node_modules[\\\]react[\\\]dist[\\\].*|website\\node_modules\\.*|heapCapture\\bundle\.js|.*\\__tests__\\.*)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: `expo start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

After doing some Googling, I found this super handy StackOverflow page (answer linked) which has several answers that talk about specific NodeJS versions that have this problem and downgrading to an earlier version (I had installed NodeJS 12.13.1, which at the time was the latest recommended version to install) fixed it. Or you could modify a specific JavaScript file that was not escaping correctly.

I decided to modify the blacklist.js file instead of downgrading my NodeJS version. The StackOverflow page linked above outlines what needs to be changed in the file. If you are using an editor like Visual Studio Code then with the syntax highlighting you will notice the difference once the \ is added to line 15 of the file. It basically goes from:

var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

to this:

var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

Now this issue may only affect Windows due to the nature of how the slashes are escaped and respected (different OS do things slightly differently). So if you encounter this problem, either downgrade your NodeJS version, or if you don’t want to do that then modify the offending JavaScript file. Also it would be worthwhile to go visit that StackOverflow page and bump up the answer. As developers we need to help each other out and share as much information as possible to help make the world a better place.

%d bloggers like this: