Skip to content

Standard Reader

Tag

Iphone

Articles and publications tagged Iphone across the Atmosphere.

82articles13publications

Articles

Publications

m.s. and bluebirdJul 14, 2026

メモ：mineoでのSIM→eSIM切替

何故できたか全く分からない。

m.s. and bluebirdJul 13, 2026

メモ：iPhoneを買い換える際の注意リスト

減ってきてはいるけどもめんどくさい。対応が必要なアプリの自動特定ぐらい欲しいな。

Neil Turner's Blog

Neil Turner's BlogJun 7, 2026

New Bluetooth hearing aids

Back in autumn 2022, following a decline in my hearing, I started wearing hearing aids. Almost four years on, and following a new hearing test, I've got new, upgraded hearing aids - and these ones have Bluetooth. Bluetooth hearing aids have been around for some time now, but were normally only available if you paid...

Neil Turner's Blog

Neil Turner's BlogMay 9, 2026

Midlife iPhone overhaul

Last month marked three years since I bought my iPhone 13 Mini. Unfortunately, it was starting to show its age a little - the battery was not holding charge very well, and the charger port was being awkward, which exacerbated the charging issue. I quite like the size of the iPhone 13 Mini, and I'm...

New Atlas - New Technology & Science NewsMar 20, 2026

Clever iPhone case adds on the back for better selfies

Continue ReadingMobile Technology

Drea

DreaMar 19, 2026

iPhone photo and video editing apps

Seeing how I cannot seem to use an actual camera to take pictures, I am doing my annual exercise of taking stock in the photography apps I use on my iPhone. When upgrading to the 17 Pro iPhone recently, I got the 1TB version, which means I have more room to store photos and videos taken at higher resolutions. For years I used Lightroom by Adobe. But ever since Adobe’s attempt to charge me to cancel a subscription, I have vowed to never use any of their services again. I also did not like having ...

photographyiPhone

Nicky Reinert - Institut für digitale HerausforderungenNov 11, 2025

Neues aus dem Innovations-Labor von Apple!

Eine humorvolle Betrachtung der neuesten Innovation von Apple: die iPhone-Socke.

Business Goose BlogJun 24, 2025

Going Light-ish

Thoughts on the confusing genius of the Light Phone 3.

Business Goose BlogJun 6, 2025

not boring camera

the most fun i have ever had with a camera app

photographyhobbies

Tedium: The Dull Side of the Internet

Tedium: The Dull Side of the InternetMay 2, 2025

The Finance Team Lost One

For years, many of Apple’s most consumer-unfriendly decisions have felt like an extension of a revenue-optimization strategy at constant risk of backfiring. Thanks to a bracing legal decision, now it has.

Tedium: The Dull Side of the Internet

Tedium: The Dull Side of the InternetSep 8, 2024

On the freedom that cellular modems gave to consumers—and how mobile companies tried to claw it back during the iPhone era.

cellularcellular networks

Chris McLeod

Chris McLeodJul 20, 2024

New Home Screen for iOS 18 Beta

Esse est percipiJul 5, 2024

iPhone-Hack: Fotos ohne automatische Nachbearbeitung aufnehmen

So ziemlich jedes Smartphone bearbeitet Fotos direkt nach der Aufnahme automatisch nach, um die Schwächen der kleinen Kamerasensoren auszugleichen. Kontrast und Sättigung werden angehoben, es wird…

Tedium: The Dull Side of the Internet

Tedium: The Dull Side of the InternetFeb 15, 2024

The Web App Switcheroo

In its quest to do as little as possible to comply with the EU’s Digital Markets Act, Apple randomly kneecaps web apps. Also: Am I sending this newsletter to fake people?

Esse est percipiFeb 12, 2024

„Momente“ sind mit dem iPhone fotografiert und bearbeitet. Verwendet wurden die Standard-iOS-Kamera-App, Focos, Camera M und Lightroom.

Tedium: The Dull Side of the Internet

Tedium: The Dull Side of the InternetJan 19, 2024

Counterfeit Computing

Discussing the piratical efforts to rip people off by counterfeiting computer hardware. It’s been happening for more than 40 years.

computersapple ii

Tedium: The Dull Side of the Internet

Tedium: The Dull Side of the InternetNov 22, 2023

The recent security drama caused by an iMessage workaround on Android shouldn’t minimize a simple fact: This is Apple’s fault.

Esse est percipiNov 18, 2023

„Momente“ sind mit dem iPhone fotografiert und bearbeitet. Verwendet wurde die Standard-iOS-Kamera-App.

Esse est percipiFeb 8, 2023

Fehler -7003 bei der HomePod-Einrichtung

Sollten Sie bei der Konfiguration eines neuen HomePods auf den oben gezeigten Fehler stoßen, liegt es wahrscheinlich daran, dass Sie in den iCloud-Einstellungen den erweiterten Datenschutz aktiviert…

Esse est percipiFeb 1, 2023

iPhone 5s, 2015

Esse est percipiFeb 16, 2021

„Momente“ sind mit dem iPhone fotografiert und bearbeitet. Verwendet wurden neben der Standard-iOS-Kamera unter anderem diese Apps: Halide, Spectre, Focos, SKRWT, Darkroom und Snapseed.

MacKuba blogSep 10, 2020

WatchKit Adventure #4: Tables and Navigation

< Previously on WatchKit Adventure… Two weeks ago I posted the first part of a tutorial about how to build an Apple Watch app UI using WatchKit, using a WKInterfaceController and a storyboard. We’ve built the main screen for the SmogWatch app, showing a big colored circle with the PM10 value inside and a chart showing data from the last few hours. Here’s the second part: today we’re going to add a second screen that lets the user choose which station they want to load the data from. So far I’ve used a hardcoded ID of the station that’s closest to me, but there are 8 stations within Krakow and the system includes a total of 20 in the region, so it would be nice to be able to choose a different one. (I initially wanted to also include a selection of the measured pollutant - from things like sulphur oxides, nitrogen oxides, benzene etc. - and I’ve actually mostly implemented it, but that turned out to be way more complex than I thought, so I dropped this idea.) The starting point of the code (where the previous part ends) is available here. Preparing the data Since the list of stations doesn’t change often, we can hardcode a list of stations with their names, locations and IDs in a plist file that we’ll bundle inside the app. The list is generated using a Ruby script, in case it needs to be updated later - you can just download the plist and add it to the Xcode project. At runtime, the list will be available in the DataStore: struct Station: Codable { let channelId: Int let name: String let lat: Double let lng: Double } class DataStore { // ... lazy private(set) var stations: [Station] = loadStations() private func loadStations() -> [Station] { let stationsFile = Bundle.main.url(forResource: "Stations", withExtension: "plist")! let data = try! Data(contentsOf: stationsFile) return try! PropertyListDecoder().decode([Station].self, from: data) } } Handling secondary screens When we want to add an additional screen to the app that shows some secondary information or less commonly used feature like this, there are generally three ways we can handle it: we can add an explicit button somewhere on the screen that opens it (usually in the bottom part) we can put it on another page in the page-based layout (e.g. like sharing and awards in the Activity app) or we can put it as an action in the menu accessed through Force Touch The third option (Force Touch menus) is going away now. In the watchOS 7 betas, Apple has removed all Force Touch interactions from the OS and their own apps, the APIs for using it in third party apps (addMenuItem in WKInterfaceController) are deprecated, and it’s highly likely that the upcoming Series 6 watch will not include it as a hardware feature. Hiding some actions in a menu had the advantage that it didn’t clutter the main view, but it also made those actions less discoverable and harder to use for those who need them. I personally always had a problem wit…

MacKuba blogAug 26, 2020

WatchKit Adventure #3: Building the App UI

< Previously on WatchKit Adventure… This is the third part of my series about building a WatchKit app that shows current air pollution level on the watch face (it started here). In this episode, we’re going to build the app’s main UI. I will be building on top of some data handling & networking code written in the previous episode about complications, so if you haven’t seen that one, you might want to at least skim through it to get some idea about what this is about. Browse through the WatchKit category to see the whole list. We’re venturing into a somewhat uncharted territory now… The WWDC talks about WatchKit are an amazing source of information and they’re great to get started (I definitely recommend watching them, especially the earlier ones, from 2015 & 2016), but once you actually start building things and run into a problem, there’s surprisingly little help available. Even StackOverflow isn’t of much use. There aren’t many books out there either that are up to date - I got one from raywenderlich.com, but it doesn’t really answer the hard questions, and it wasn’t updated since watchOS 4; Paul Hudson has another, and that’s pretty much it. I’ve tried to figure out some things myself, but some questions are left unanswered. If you know how to solve anything better than I did, please let me know in the comments. The two frameworks watchOS SDK launched first in 2015 with a new UI framework called WatchKit. It was a very different framework than what we knew from macOS and iOS, a framework specifically designed for the Watch and all its inherent and temporary limitations - and also limited in what it could do and what you could do with it. It got people excited, but also very quickly frustrated, once they’ve run into these limitations. It didn’t help that Apple’s own apps were very obviously doing some things in the UI that weren’t possible to external developers, clearly using some internal APIs Apple needed to build more powerful apps, but which they didn’t want to share with us. So of course the hearts of Watch developers started beating faster when we heard the brief mention “… and a new native UI framework” during the 2019 keynote - said almost as if we were supposed to miss it. Of course about two hours later we’ve learned that this new framework was SwiftUI, built not only for watchOS (although that’s how the whole thing started, apparently!), but for all Apple platforms. A thing that would completely change Apple platform development. However, as people who have rushed to try out this new framework quickly discovered, SwiftUI as released in the iOS 13 SDK was “a pretty solid version 0.7” - a massive step forward of course, especially on watchOS, but still more of a beta. The “version 2.0” released this June seems like a very decent update, but it’s not stable yet and at this point it’s still unclear if it solves most of the issues that people had with the first release. So here we are, with two frameworks, an old one that’s ver…

MacKuba blogAug 17, 2020

SwiftUI betas - what changed before 1.0

In the last few weeks I’ve been trying to catch up on SwiftUI - watching WWDC videos, reading tutorials. Not the new stuff that was announced 2 months ago though - but the things that people have been using for the past year. Last June, like everyone else I immediately started playing with SwiftUI like a kid with a new box of Legos. In the first month I managed to build a sample Mac app for switching dark mode in apps. However, after that I got busy with some other things, and never really got back to SwiftUI until recently, so by the time the “version 2” was announced at the online-only WWDC, I’ve already forgotten most of it. So in order to not get this all mixed up, I decided to first remember everything about the existing version, before I look at the new stuff. Back then, when I was watching all the videos and doing the tutorial, I was taking a lot of notes about all the components, modifiers and APIs you can use, every single detail I noticed on a slide. However, I was surprised to see how many of those things I wrote down don’t work anymore. After the first version that most people have played with and that the videos are based on, there were apparently a lot of changes in subsequent betas (especially in betas 3 to 5). Classes and modifiers changing names, initializers taking different parameters, some things redesigned completely. And the problem is that all those old APIs are still there in the WWDC videos from last year. But WWDC videos are usually a very good source of knowledge, people come back to them years later looking for information that can’t be found in the docs, Apple even often references videos from previous years in new videos, because they naturally can’t repeat all information every year. This was bothering me enough that I decided to spend some time collecting all the major changes in the APIs that were presented in June 2019, but were changed later in one place. If you’re reading this in 2021 or 2022 (hopefully that damn pandemic is over!), watching the first SwiftUI videos and wondering why things don’t work when typed into Xcode - this is for you. Here’s a list of what was changed between the beta 1 from June 2019 and the final version from September (includes only things that were mentioned in videos or tutorials): NavigationButton Appeared in: “Building Lists and Navigation” tutorial, “Platforms State of the Union” ForEach(store.trails) { trail in NavigationButton(destination: TrailDetailView(trail)) { TrailCell(trail) } } Replaced with: NavigationLink ForEach(store.trails) { trail in NavigationLink(destination: TrailDetailView(trail)) { TrailCell(trail) } } PresentationButton / PresentationLink Appeared in: “Composing Complex Interfaces” tutorial, “Platforms State of the Union” .navigationBarItems(trailing: PresentationButton( Image(systemName: "person.crop.circle"), destination: ProfileScreen() ) ) Replaced with: PresentationLink, which was lat…