Things I want to accomplish: ✅

‎1. Get data from XML file into HealthKit
‎2. Show HealthKit workout route on the map
‎3. Visualize Heart rate and Speed/Pace

One of the most exciting breakthroughs in modern tech medicine is getting your physical data, biometric data into the EMR (electronic medical record) and into your doctors hands. It first arrived on the mobile market with HealthKit. HealthKit was introduced by Apple in iOS 8 (mid 2014), a framework that enables developers to interact with health and fitness data on iOS devices. It acts as a centralized repository, collecting data from various sources such as the iPhone’s built-in sensors, third-party devices, and user input. This wealth of information includes but is not limited to steps taken, heart rate, sleep patterns, nutrition, and more. The user has granular access control and it’s all opt-in. Data storage of it doesn’t need to be HIPAA compliant and it is the consumer’s responsibility to keep their data secure.

Read on →

Where to begin! Where to begin…

Localization is something that occurs in every project I encounter. Implementing localization can be a bit bothersome for developers, but it can make users feel respected and cared for. I found that having a list of useful tips that cover most aspect of localization is nice to have, especially as it goes through regular Apple API updates. So I created this post as my memory of legacy and current state of possible best practices in localization. There is a slight distinction between internationalization and localization:
Internationalization — the process of making your app able to adapt to different languages, regions, and cultures.
Localization — the process of translating your app into multiple languages. So, in total it depends on context, and namely on this elements:

• Singular and plural in the text
• User gender (or consensus declaration)
• Platforms: Web, Android, iOS
• Project objective for which the translation is being done.

Read on →

A good section of this post is about the research + a project “Diagram” and steps I wish somebody told me upfront. Before I dive into Auto Layout, should I remind you also of legacy in frames 😝, masks — you always had to tell buttons and other controls how big they should be, either by setting their frame or bounds properties or by resizing them in Interface Builder. But it turns out that most controls are perfectly capable of determining how much space they need, based on their — content. 🌈🦄🌈 🕵️‍♀️ 🕵️‍♀️ Note: There is a tool Scherlock — it lets you edit views and layout constraints in real time, simulate running on other devices, and jump straight to the source code, all from your iOS Simulator — zero configuration required only $$ after trial.

Things I want to accomplish:⏎ — Solve errors in layout IB Auto Layout — Solve errors in code Auto Layout

Read on →

Networking code can definitely be improved. Thanks Apple! No third parties here! 👌 So since Swift 4 we got Codable with Decodable and Encodable protocols that provide support for native class (reference type), struct and enum as well (value types) all concrete data types…

First of all Codable is defined as typealias Codable = Decodable & Encodable and we go for two required protocols:

• Decodable: to parse JSON (get response)
• By decoding the JSONData we will receive/read the data
  1. Encodable: to generate JSON (post response)
• To convert your codable type into Data.

Read on →