#ios
-
My GPS tracking app is live in the App Store! It's ugly, but it works, and now you can use it too! https://overland.p3k.io
-
Day 64: Documentation and Fixes for my GPS Logger App #100DaysOfIndieWeb
I track my location continuously using an iOS app I wrote a few years ago. The app is not published on the app store, but it is open source. Today I added a bunch of documentation describing what all the controls in the interface are for.
The settings screen is somewhat overwhelming, mostly because this is actually intended to be an app for learning what the various iOS location APIs do.
So now the readme file has a description of each of these controls.
Head over to the readme for the details! https://github.com/aaronpk/GPS-Logger-iOS#documentation
I also added a new control, "points per batch", which controls how many location updates are sent to the server in each HTTP request. Prior to this setting, it was always sending 200, which works well but sometimes causes problems. When I take a long plane flight and queue up thousands of points on the device before I am back to a data connection, sending them 200 at a time actually takes quite a while to send them all. Now I can set the batch size to 1000 which should flush them much more quickly.
During this process, I also discovered a weird bug where none of the controls in the settings screen could be tapped! I suspect this is some iOS 10 API change that caused this, since I haven't changed anything about the app since I used it on iOS 9. I still don't know the underlying cause, but I was able to fix it by removing one level of nesting of the UI elements. Previously, a ScrollView contained a ContentView which contained the StackView that has all the controls. I removed the ContentView from the middle and now the buttons are tappable again. No idea what went wrong! I am clearly not an iOS developer.
-
How to build cross-platform mobile apps using nothing more than a JSON markup (medium.freecodecamp.com)
-
macOS 10.12 Sierra: The Ars Technica review | Ars Technica (arstechnica.com)"Here’s how it works (note that any time you see “Mac” below, the feature also works on iDevices running iOS 10): Text or some other item is copied on one Mac. The device then advertises over Bluetooth that it has something in its clipboard, just as it would do if it had content available via Handoff. Unlike Handoff, though, there's no visual indicator on other Macs or iDevices that anything is ready to copy. Hit paste on the other Mac. There's a pause that accompanies the action—nearly unnoticeable for a snippet of text or a link but long enough to prompt a little progress bar popup for larger images or big chunks of text—during which Mac #2 requests the contents of Mac #1's clipboard, and Mac #1 sends it over. Though both of your devices need to be signed in to the same iCloud account to trust each other, your data never appears to touch Apple's servers—like Handoff, all communication is local. This also means that Bluetooth and Wi-Fi have to be enabled on both devices, and both devices need to be within range of each other for copying and pasting to work. You won't necessarily need an active Internet connection."
-
Jason Client - iOS client for your web app! (www.jasonclient.org)This could be a way to enable some simple #indieweb interactions in an iOS client
