<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CI&amp;T Australia on Medium]]></title>
        <description><![CDATA[Stories by CI&amp;T Australia on Medium]]></description>
        <link>https://medium.com/@ciandt-au?source=rss-92c296a8f221------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Me--1H0AcDcCQ8aorQwqog.png</url>
            <title>Stories by CI&amp;amp;T Australia on Medium</title>
            <link>https://medium.com/@ciandt-au?source=rss-92c296a8f221------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:49:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ciandt-au/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What’s New in MapKit? An Overview of the Latest Advancements]]></title>
            <link>https://medium.com/ciandt-techblog/whats-new-in-mapkit-an-overview-of-the-latest-advancements-da248f385e97?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/da248f385e97</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[maps]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 23:24:45 GMT</pubDate>
            <atom:updated>2023-03-14T23:27:42.317Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/prashant911/"><em>Prashant Singh</em></a><em> is a consultant and iOS Specialist who loves helping clients design, architect and implement mobile apps using the latest technologies.</em></p><p>Apple’s MapKit framework, which provides mapping and location-based services to iOS applications, has always been an important part of the iOS ecosystem. Apple has been consistently working on improving its mapping service, and with the introduction of iOS 16, Apple has added several new features to MapKit that will make it even more powerful and user-friendly. In this blog, we will take a closer look at some of the most notable changes and additions.</p><h3>1: Detailed 3D city experience:</h3><p>The realistic 3D city view is available as a part of the framework. It provides an immersive and interactive experience for users and includes detailed buildings, roads, and other landmarks. This new feature makes it easier for users to get a better understanding of the terrain and surrounding area and will be especially useful for city exploration and navigation.</p><p>To enable it, there is no need to write any lines of code. The app should be built using iOS 16 SDK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*9Mql0O5_ulg0bRdV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*jKrTIAZDuYAOe1p3" /></figure><h3>2: Real elevation details</h3><p>With iOS 16, MapKit now provides detailed information on the elevation of different locations on the map including overpasses and bridges. This can be especially useful for outdoor enthusiasts and fitness enthusiasts who want to know the elevation gain and loss of their route. The elevation information is displayed in real-time as users navigate the map, allowing them to easily see the changes in elevation along their route.</p><p>To enable the elevation details, the elevationStyle property should be set while configuring the map view object.</p><pre>mkMapView.preferredConfiguration = MKStandardMapConfiguration (elevationStyle: .realistic, emphasisStyle: .default)</pre><p>In the above block of code, elevationStyle is set as realistic to enable elevation details on the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*nJ3djceVMCKTWMz5" /></figure><p>To preserve the elevation details while adding a navigation polyline to the map, the route returned by MKDirections class should be used.</p><pre>let directionRequest = MKDirections.Request ()<br>directionRequest.source = MKMapItem (placemark: routeStart)<br>directionRequest.destination = MKMapItem (placemark: routeEnd)<br>Task {<br>let direction = MKDirections (request: directionRequest)<br>do {<br>let directionResponse = try await direction.calculate()<br>for route in directionResponse.routes {<br>mkMapView.addOverlay (route.polyline, level: .aboveRoads)<br>}<br>} catch { return }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*uEzGJ1ZvWikUXdND" /></figure><p>The MKDirections polyline route is also visible if it is hidden behind an object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*kLOOUdV0t--Im586" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*j9jAIWcMAlC_TvM_" /></figure><h3>3: Blend modes in overlays</h3><p>This new feature allows the developers to display custom map overlays in unique and creative ways. Through blend modes, an overlay can be made brighter while making the other areas grey. The map content beneath the overlay like trees and roads is also affected by the overlay colour while using blend mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*stxZrx6mvYOSLrad" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*H28V4r4Ppiej4CNx" /></figure><p>To enable blend mode, the blendMode property needs to be set while creating the overlay renderer object.</p><pre>let renderer = MKPolygonRenderer(overlay: overlay)<br>renderer.fillColor = .gray<br>renderer.strokeColor = .gray<br>renderer.lineWidth = 1.0<br>renderer.blendMode = .hue</pre><h3>4: LookAround API support</h3><p>iOS 16 brings Look Around to the MapKit. Look Around provides an immersive street-level view of the map, and it offers an incredible level of detail. It leverages 3D models to provide a level of realism like no other map.</p><p>Look Around uses its view controller (MKLookAroundViewController) to present the street view. A scene request using MKLookAroundSceneRequest class and coordinates needs to be placed. If the request is successful, the returned view controller is used to show the street view.</p><pre>let viewController = MKLookAroundViewController()<br>viewController.badgePosition = .topLeading<br>viewController.isNavigationEnabled = true<br>viewController.pointOfInterestFilter = .excludingAll<br>viewController.showsRoadLabels = false<br>let location = CLLocationCoordinate2D (<br>latitude: Constants.routeStartLatitude,<br>longitude: Constants.routeStartLongitude<br>)<br>let sceneRequest = MKLookAroundSceneRequest (coordinate: location)<br>Task {<br>do {<br>viewController.scene = try await sceneRequest.scene<br>} catch {<br>viewController.scene = nil<br>}<br>}<br>return viewController</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*ufXXcEaTVPywo2hN" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/0*a1XZcUovVOCSTPBH" /></figure><h3>5: Pricing</h3><p>Only standard Apple developer membership (AUD149/year) is required to access MapKit and its features for iOS development. For using MapKit JS for web development, a daily limit of 250,000 map views and 25,000 service calls per Apple Developer Program membership is provided for free.</p><h3>6: Challenges and Limitations:</h3><p>Although these features bring many benefits, they also come with some limitations. These limitations range from the availability of the features to the dependency on other Apple frameworks. Therefore, it’s important to consider these factors when considering MapKit as the mapping platform for your app.</p><p>Some potential challenges and limitations include:</p><ol><li>Most features except the detailed 3D city are present in iOS 16 and above.</li><li>Detailed 3D city experience requires A12 Bionic and later chipset.</li><li>At present, the detailed 3D city experience is only present in a few cities.</li><li>Elevation details are not available when adding any overlay to the map.</li><li>Map overlay boundaries are not clearly defined when viewing in 3D mode.</li><li>To use the full power of blend modes, knowledge of the Core Graphics framework is needed.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da248f385e97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/whats-new-in-mapkit-an-overview-of-the-latest-advancements-da248f385e97">What’s New in MapKit? An Overview of the Latest Advancements</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Live Data Scanning on iOS: A Quick Look at Apple’s VisionKit Framework]]></title>
            <link>https://medium.com/ciandt-techblog/live-data-scanning-on-ios-a-quick-look-at-apples-visionkit-framework-682ea50fa04b?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/682ea50fa04b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ios-apps]]></category>
            <category><![CDATA[maps]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 23:17:05 GMT</pubDate>
            <atom:updated>2023-03-14T23:17:05.638Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/prashant911/"><em>Prashant Singh</em></a><em> is a consultant and iOS Specialist who loves helping clients design, architect and implement mobile apps using the latest technologies.</em></p><p>Apple’s VisionKit framework allows the developer to use the device camera to scan data present in images. The framework is capable of scanning machine-readable codes and can be configured to look for specific content in the text (E.g. email, street address, phone number, URL, shipment tracking number, and date). With the introduction of iOS 16, data scanning is possible with a live camera feed. In this blog, we will look at the implementation and various configurations of the live data scan using the camera video feed.</p><h3>Scanning the Data:</h3><p>Data scan is performed with the help of the “DataScannerViewController” class introduced in iOS 16.</p><p>An object of DataScannerViewController needs to be created after setting the required parameters containing the scan options.</p><p><strong>Note:</strong> In SwiftUI, the DataScannerViewController needs to be wrapped using UIViewControllerRepresentable as it is a part of UIKit.</p><pre>let scannerViewController = DataScannerViewController (<br>recognizedDataTypes: [.text(), .barcode(symbologies: [.aztec, .qr])],<br>qualityLevel: .fast,<br>recognizesMultipleItems: true,<br>isPinchToZoomEnabled: true,<br>isGuidanceEnabled: true,<br>isHighlightingEnabled: true)</pre><h3>Scan Options:</h3><p>The following scan options should be configured before starting the scan.</p><ul><li><strong>Recognized Data Types:</strong> It takes both barcodes and textual types. The types can be further configured depending upon the language and content for text and symbology for the barcode.</li><li><strong>Quality Level:</strong> Fast, balanced or accurate.</li><li><strong>Recognises Multiple Items:</strong> Recognise all the groups of items in the camera viewfinder or only one.</li><li><strong>Pinch to Zoom:</strong> Use the pinch gesture to zoom in and out of the live feed. When zooming, it uses all the cameras (Main, Ultra Wide and Telephoto) present on the device.</li><li><strong>Enable Guidance:</strong> Set this to true if the app should provide text cues when scanning the items, e.g., “Slow down.” when moving the phone fast.</li><li><strong>Highlighting enabled:</strong> Highlight the recognised items</li></ul><p>To start the scan, the “startScanning()” method of the created view controller object is used.</p><pre>try? scannerViewController.startScanning()</pre><p>In the below image, the scanned text is printed on the second half of the screen on a custom view. In the first half, the view presented by DataScannerViewController is shown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/0*7TtpcVm0YUUZ2HgS" /></figure><h3>Specific text content scan</h3><p>To specify the text content type to be scanned, the required text content type should be specified in the “recognizedDataTypes” parameter while initialising the DataScannerViewController object.</p><pre>let scannerViewController = DataScannerViewController (<br>recognizedDataTypes: [.text (textContentType: .fullStreetAddress),<br>.barcode (symbologies: [.aztec, .qr])],<br>qualityLevel: .fast,<br>recognizesMultipleItems: true,<br>isHighlightingEnabled: true)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/0*rt2HKsU6y6euzqfO" /></figure><h3>Single item scan</h3><p>Single-item scanning mode can be configured using the “recognizesMultipleItems” property in the DataScannerViewController initialiser.</p><pre>let scannerViewController = DataScannerViewController (<br>recognizedDataTypes: [.text(), .barcode (symbologies: [.aztec, .qr])],<br>qualityLevel: .fast,<br>recognizesMultipleItems: false,<br>isHighlightingEnabled: true)</pre><p>In single-item scan mode, the required item can be selected by a tap if multiple items are present.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*RJO0PXWwmWbIwZFg" /></figure><h3>Parsing the Data</h3><p>The scanned results are provided in delegate methods (didAdd, didTapOn, didRemove) of the DataScannerViewControllerDelegate protocol. The items are represented inside the RecognizedItem enum containing the recognised data type (barcode or text).</p><pre>func dataScanner (_ dataScanner: DataScannerViewController, didTapOn item: RecognizedItem) {<br>tappedItem = item<br>}<br>func dataScanner (_ dataScanner: DataScannerViewController, didAdd addedItems: [RecognizedItem], allItems: [RecognizedItem]) {<br>recognisedItems.append(contentsOf: addedItems)<br>}<br>func dataScanner (_ dataScanner: DataScannerViewController, didRemove removedItems: [RecognizedItem], allItems: [RecognizedItem]) {<br>recognisedItems = recognisedItems.filter { item in<br>!removedItems.contains (where: {$0.id == item.id })<br>}<br>}</pre><p>To get the value of the scanned text from the RecognizedItem enum, the “transcript” property needs to be accessed. For barcodes, “payloadStringValue” contains the scanned value in the String form.</p><pre>switch item {<br>case .barcode (let barcode):<br>print (barcode.payloadStringValue ?? &quot;Unknown barcode&quot;)<br>case .text (let text):<br>print (text.transcript)<br>@unknown default:<br>print (&quot;Unknown item&quot;)<br>}</pre><h3>Limitations</h3><p>While VisionKit is a powerful and versatile framework, it does have some limitations that developers should be aware of when designing their apps. Some of these limitations are given below.</p><ol><li>Scanning using the live camera feed is only available in iOS 16 and above.</li><li>The device should have a minimum of an A12 Bionic chipset.</li><li>The framework struggles when scanning for the text that is not present in a straight line.</li><li>When scanning for multiple complex items such as Version 40 QR codes, the device needs to be held very still.</li><li>Not all languages are supported by text scanning. As of iOS 16, the following languages are supported: English, French, Italian, German, Spanish, Portuguese, Chinese, Japanese, and Korean.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=682ea50fa04b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/live-data-scanning-on-ios-a-quick-look-at-apples-visionkit-framework-682ea50fa04b">Live Data Scanning on iOS: A Quick Look at Apple’s VisionKit Framework</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering WatchOS Complications: The Ultimate Guide for Swift Developers]]></title>
            <link>https://medium.com/ciandt-techblog/mastering-watchos-complications-the-ultimate-guide-for-swift-developers-96433b0167ca?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/96433b0167ca</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[apple-watch]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[wearables]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 22:43:02 GMT</pubDate>
            <atom:updated>2023-03-14T22:43:02.740Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/debashree-joshi-43004767/"><em>Debashree Joshi</em></a><em> is a consultant and iOS Specialist with a passion for helping clients create user-friendly mobile applications.</em></p><p>Do you ever find yourself constantly checking your phone for updates or reminders? Well, with <a href="https://developer.apple.com/documentation/clockkit/creating_complications_for_your_watchos_app">WatchOS complications</a>, you can access important information with just a glance at your wrist. These small widgets provide a range of functions, from displaying the weather and your heart rate to showing upcoming appointments and more.</p><p>The concept of complications comes from horological and chronograph mechanical watches, which feature additional dials and displays on the watch face beyond the basic timekeeping function. In 2015, Apple introduced the idea of complications to their smartwatches, adding even more functionality to the already powerful device. Today, these complications are widespread on Apple Watch faces and provide an even more seamless experience for users.</p><h3>TaskLister App</h3><p>TaskLister is an app that has taken full advantage of several types of complications, including rectangular, circular, extra-large, and corner circular complications. These complications offer different ways to display the app’s data, making it easier for users to stay organised and focused on their daily tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kt_asxkSdH6Axu7d" /></figure><p>Using TaskLister as an example, we can create complications that display important data from the app. The app contains information about the task, such as the task name, task description, location, time, and category. Each task card is colour-coded according to the priority level, with high-priority tasks appearing in green, medium-priority tasks in blue, and low-priority tasks in red. Low-priority tasks are indicated with a single exclamation mark, medium-priority tasks with a double, and high-priority tasks with a triple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fN81uRA6ZzENlJrR" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eKNQA0NDZURUB4Rb" /></figure><p>For instance, a circular complication can show users that there are 29 minutes left before the next task begins which is perfect for showing countdowns or progress bars. Meanwhile, if users prefer a bigger and bolder view of their task information, an extra-large complication may be the way to go. With this option, they can see that there is 1 hour and 14 minutes left before the next task, which happens to be “Grocery” starting at 14:26.</p><p>In addition to these essential details, the corner circular complication offers a unique feature with a red progress bar indicating that the task is of low priority and will begin in 29 minutes. On the other hand, a rectangular complication is ideal for displaying detailed information, such as the next task will begin in 44 minutes and 59 seconds, with the task name “Workout” starting at 13:57.</p><h3>Adding Complications to Your App:</h3><p>To create WatchOS complications, developers can use the CLKComplicationDataSource protocol to provide data to WatchOS. The data is displayed on the Watch face, and it updates periodically, ensuring that the data is always up to date. The ClockKit framework provides the necessary classes and methods to create and manage complications. Developers can use templates to create complications or create custom complications that provide unique designs and features. Developers can easily add complications to their watchOS app by following the documentation provided by Apple. Here are some resources for developers to get started with adding complications to their apps:</p><ul><li><a href="https://developer.apple.com/documentation/clockkit/creating_complications_for_your_watchos_app">Apple’s documentation on complications in watchOS</a></li><li><a href="https://developer.apple.com/documentation/clockkit/building_complications_with_swiftui">Apple’s guide on building complications with SwiftUI</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2020/10046/">A video on creating complications for your watchOS</a></li></ul><p>Adding complications to the watch face allows the user to customise their experience and get quick access to important information. Whether it be tracking the daily progress, keeping tabs on upcoming appointments, or simply checking the weather, these small widgets can help simplify their day-to-day life. By using TaskLister as an example, we can see how different types of complications can be used to display important data on the Watch face. The CLKComplicationDataSource protocol and the CLKComplicationTimelineEntry framework make it easy for developers to create their own complications and customise the data that is displayed. Ultimately, WatchOS complications are an essential tool for Swift developers to take their apps to the next level and deliver an exceptional user experience.</p><p><strong>Have you used WatchOS complications in your app? Share your experience in the comments below!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96433b0167ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/mastering-watchos-complications-the-ultimate-guide-for-swift-developers-96433b0167ca">Mastering WatchOS Complications: The Ultimate Guide for Swift Developers</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our experience with Mac Catalyst]]></title>
            <link>https://medium.com/ciandt-techblog/our-experience-with-mac-catalyst-226c236b9184?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/226c236b9184</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[web-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Sun, 13 Nov 2022 23:39:20 GMT</pubDate>
            <atom:updated>2022-11-13T23:39:20.856Z</atom:updated>
            <content:encoded><![CDATA[<h4>This blog from Darren Mariadas and Justin Maciburko from our iOS team gives a summary of their implementation of Mac Catalyst, and how they took a client from having no Mac presence to being #3 on the Mac App Store (Health &amp; Fitness).</h4><p>During WWDC 2018, Apple’s annual ‘Worldwide Developers Conference’, Project Catalyst was announced to the wider apple developer community. Formerly known as Project Marzipan, Catalyst was Apple’s promise to port the arguably more popular iPadOS app ecosystem to MacOS, by allowing the development of a universal app that can act as both a native iPadOS application and also an indistinguishable MacOS application. This raised a lot of concerns around the challenges that can arise in doing so and a lot of developers simply weren’t convinced that it would be worthy from both a time and effort point of view. After all, can it really be all that simple to translate the user experience from a touch based interface to mouse/pointer based one? Here’s what Apple says on <a href="https://developer.apple.com/mac-catalyst/">their documentation</a>:</p><blockquote><em>“Your newly created mac app runs natively, utilising the same frameworks, resources, and runtime environment as apps built just for Mac. Fundamentally, Mac desktop and windowing features are added, and touch controls are adapted to the keyboard and mouse. By default, your app will scale to match the iPads resolution. You can choose “Optimise interface for Mac” to use the Mac idiom, running your app using the native resolution of Mac. This gives you full control of every pixel on the screen and allows your app to adopt more controls specific to Mac, such as pull-down menus and checkboxes.”</em></blockquote><p>We couldn’t wait to dip our feet into this new technology and see if it really is as simple to port an existing iPad application of ours, over to MacOS.</p><h3>The perfect client</h3><p>We have a client who felt like a natural fit for Catalyst, as a major goal of their app was to reach as many people as possible. The app in question uses the collective power of smartphones to fast track research by downloading tiny parts of huge research projects from the cloud, calculating them, and sending the results back to the specified research team. With more people powering projects, the faster they’ll be completed — and in turn, more research can be done.</p><p>The amount of time estimated to release a working Mac Catalyst app was crucial to whether we would be able to go ahead or not. To reduce the overhead of needing new image assets that scale well on a desktop, we made the decision to fix the window to an ideal size when built for the platform. However, doing this still left some issues that needed to be resolved before we felt comfortable releasing to users.</p><p>As parts of the UI (and in some instances, logic) would need to be varied only for Mac, we leveraged extensions to reduce the code noise this would bring while retaining clarity. For example, this extension on Bool used to wrap a Mac Catalyst preprocessor check:</p><figure><img alt="A snippet of Catalyst code" src="https://cdn-images-1.medium.com/max/750/0*wdTl3KxXuGjL3rGX" /></figure><p>This allowed us to quickly and easily add catalyst specific conditions where needed:</p><figure><img alt="A snippet of Catalyst code" src="https://cdn-images-1.medium.com/max/750/0*oKU-RXbXCb5NOpLq" /></figure><p>More specifically to SwiftUI, there were times that we needed view modifiers conditionally for MacOS. For this, we used an extension on view that allows us to pass in a Bool that, if true, applies the given transformation to that view. This works quite smoothly in conjunction with the Bool extension above:</p><figure><img alt="A snippet of Catalyst code" src="https://cdn-images-1.medium.com/max/750/0*gwca3Ht0vRw3FXC-" /></figure><p>And when utilised:</p><figure><img alt="A snippet of Catalyst code" src="https://cdn-images-1.medium.com/max/750/0*rxAj9_Ki0hqGewJ_" /></figure><p>Making use of these extensions allowed us to tweak and polish the Mac application to get it just how we want — with a user experience that is more or less the one you would have when running the mobile version of the app.</p><p>Another challenge faced when building for Catalyst was dependencies. Some libraries that you rely on and leverage may not yet have the support for Catalyst which leads to an inability to compile the app when these libraries are included.</p><p>In our case, we use CocoaPods and needed a way to include a few pods for iOS only. If using pods, there exists a library of Ruby extensions to help you configure the pods project to achieve this. It enables you to add a function to your podfile where you can reference which pods you want just for iOS or just for Mac.</p><p>An example podfile snippet from the project Github:</p><figure><img alt="A snippet of Catalyst code" src="https://cdn-images-1.medium.com/max/750/0*Q4f0QhxCVo_2DGCn" /></figure><p>The project is maintained by fermoya and can be found at the following link:</p><p><a href="https://github.com/fermoya/cocoapods-catalyst-support">https://github.com/fermoya/cocoapods-catalyst-support</a></p><p>In retrospect, making this app available on Mac using Catalyst was a great learning experience for all involved. While not quite as simple as checking a box and shipping a shiny new Mac app — it comes pretty close as all of the heavy lifting done behind the scenes means that the majority of the app functionality simply works out of the box. For any remaining issues, the support and documentation around Catalyst was somewhat sparse but improving.</p><p>As Catalyst gains maturity we would expect more quirks will continue to be ironed out as well as further support and community growth that will make Catalyst more seamless and attractive in the future. Even so, we consider using Catalyst in its early stages a big win — with the ability to reach more new users and provide existing ones with greater flexibility in how they choose to power their chosen research project!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*AolI1GLUPmv6qenEONZ1Gg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=226c236b9184" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/our-experience-with-mac-catalyst-226c236b9184">Our experience with Mac Catalyst</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expo]]></title>
            <link>https://medium.com/ciandt-techblog/expo-a105ef0d5930?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/a105ef0d5930</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[expo]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Thu, 30 Sep 2021 03:56:19 GMT</pubDate>
            <atom:updated>2021-09-30T03:56:19.352Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/mazhar-morshed/">Mazhar Morshed</a> &amp; <a href="https://www.linkedin.com/in/kuldeepsuhag/">Kuldeep Suhag</a>, React Native Engineer, <a href="https://www.transpire.com/">Transpire</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oew2OMAHqprZlE1JHDdAhA.jpeg" /></figure><p>When people hear about React Native, they often have heard about it or maybe have played around with it. However, when it comes to Expo, they may not have heard of it, but if they have played around with react native, it could highly likely be the case that they have used Expo.</p><p>When a user is going through the official development docs of React Native, they go through the introductory docs going over the core concepts, including what React Native is as well as a few core components and how to go about styling them inside a few widgets that render the code to UI side by side.</p><p>That widget is an Expo widget, and the next guide document the user gets to is the screen underneath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*as_B5lxEwGNDmOUqMAlFKA.png" /><figcaption>The first page for setting up a development environment on official react native dev docs:<a href="https://reactnative.dev/docs/environment-setup">Setting up the development environment · React Native</a></figcaption></figure><p>From here, when the official documents always start the user off with using expo, as well as using it in widgets for showcasing and tutorializing its functionality, that gives weight to its importance on the wider React Native.</p><h3>Scope of Expo</h3><p>Anyone that has used Expo understands the title that comes in on Expo’s home page, <a href="https://expo.io/">“Make any app. Run it everywhere.”</a>, which covers exactly what Expo aims to do. Directly from React Native’s home page, its header <a href="https://reactnative.dev/">“Learn once, write anywhere”</a> symbolises where Expo fits in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*1MfKKI5LkAHXpA2QPSLfmw.png" /><figcaption>“Make any app. Run it everywhere.”<a href="https://expo.io/">Expo</a></figcaption></figure><p>React Native will be able to translate a few screens of UI code into app ready code. However, since React Native is packaged inside a native app with a bridge to get updates from the JS thread, in the end, it means creating the app itself is not any different from making a normal Android or iOS app with a few android screens or iOS screens. This, of course, is a <a href="https://reactnative.dev/docs/next/native-modules-intro">selling point</a> due to the ability to drop into native when required and why the transition from native to React Native apps or vice-versa makes react-native one of the best options for hybrid development in the market.</p><p>Expo here gives users of React Native the option to forego this benefit and let it handle that whole process (while also allowing the option to eject in the case that native modules needed).</p><p>This allows developers to focus on the interactive and functional part of the app without having to worry about app assets such as icons and splash screens, dealing with libraries that require native management (<a href="https://rnfirebase.io/">firebase</a>), dealing with upgrading and handling native libraries, configuring Gradle or .plist files, modifying central Kotlin/Java or ObjectiveC/swift files.</p><h3>Expo Features</h3><p>Expo covers many features, especially because they have been in the scene for quite some time alongside React Native. We won’t go into details into all of them but will only go over briefly the larger features that would impact the developers the most.</p><h3>Expo Snack (React Native + Expo Sandbox)</h3><p>In production, this would not be used much but listing it here due to the amount of effort the expo team has put into making this unique service (could be useful as a testing/demoing tool, as is the case with many react native teams such as UI/navigation frameworks).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_dUhr7kF7F12xw5GuBr4jg.png" /><figcaption>Example generated snack with preview and editor. <a href="https://snack.expo.io/">Snack — React Native in the browser</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Iuaajn999f2VwWs0DO-q1Q.png" /><figcaption>This can also be used to create an embeddable editor</figcaption></figure><h3>Expo Go</h3><p>Because Expo apps are very much self-contained in the expo ecosystem and it handles all the native aspects to help with testing, showcases and experiments, <a href="https://expo.io/client">Expo Go</a> is an app for <a href="https://play.google.com/store/apps/details?id=host.exp.exponent">android</a> and <a href="https://apps.apple.com/au/app/expo-go/id982107779">iOS</a> which allows downloading apps published onto Expo’s cloud servers.</p><p>This whole process speeds up iterations quicker than going through PlayStore/TestFlight for testing if the user has expo go installed. If an app has been published under a ‘default’ release channel, then this app is accessible instantly if the developer does a simple expo publish</p><p>expo publish</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*PIkWxUk7XDlpRvWq9tEvkQ.png" /><figcaption>Expo go iOS <a href="https://expo.io/client">Expo</a></figcaption></figure><p>The only problem we encountered was trying to use this for multiple release channels, for example, a development, staging and production environment. It will only host default channels. There are definitely work around here where the developer can set up multiple different apps with different app signatures but out of the box, and if it was tied to environments tied to AppStore/PlayStore apps, then it requires some extra thought.</p><p>As explained in their <a href="https://blog.expo.io/expo-go-a-new-name-for-the-expo-client-4684a2709904">introductory blog</a> for the release of the Expo Go client, the app contains all the expo standard SDK and will host any javascript modules packaged with the expo app bundle.</p><h3>Expo SDK and CLI</h3><p>As we spoke about in the scope of Expo, one of the aims of it was to abstract away having to deal with the native side of React Native complete. In this case of a setup for a few of the most popular third-party services that require native configuration such as <a href="https://docs.expo.io/versions/latest/sdk/firebase-analytics/">Firebase Analytics</a>, <a href="https://docs.expo.io/guides/using-sentry/">Sentry</a> and other device-specific methods such as device <a href="https://docs.expo.io/versions/v41.0.0/sdk/constants/">constants</a>.</p><p><a href="https://docs.expo.io/versions/latest/">API Reference — Expo Documentation</a> as a reference to their API docs should be checked for capabilities. If there are missing capabilities, then it makes sense not to use Expo in these scenarios, especially when it comes to native modules that wouldn’t support it.</p><p>The CLI includes ways of handling the expo cloud services and CI/CD within the template of Expo, but it also includes a starter template for expo apps with expo init.</p><p>Another great benefit, along with many of its other features, when running the bundler, expo gives a more interactive dashboard for running apps which allow a way of doing standard React Native bundler activities in a GUI dashboard; reading javascript logs, opening and running on emulators, publishing to Expo so that physical device testing can be done without android studio or code or sharing the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*hg8mDG9Y32uXgh4gbE30VA.png" /><figcaption>What you see when you run the metro bundler with Expo.</figcaption></figure><p>Because of the Expo SDK/CLI, which represents much of the reason the native side of React Native is abstracted away, dealing with expo rather than RN + Android or RN + iOS, is a core reason we have used it for rapid prototyping to save development/deployment time.</p><h3>Expo Eject</h3><p>There are cases when a developer needs to add some native functionality to a project. Expo project is a Pure JS project which does not provide a native dropdown for both Android and iOS.</p><p>To expose the native modules of both the platform we need to use ExpoKit.</p><p>To eject the native modules use the command:</p><p><em>expo eject</em></p><p>There are some reasons when you don’t want to expose the native modules:</p><ul><li>Once the native modules are ejected, we won’t be able to publish both android and iOS on their store using expo build.</li><li>If you have implemented expo-push notification, once ejected your Expo wont be able to manage push-notification. You might want to create your push notification pipeline.</li></ul><h3>Expo Application Services</h3><p>Along with their SDK and CLI, which are installed for local developer machines, Expo also contains their online service, which contains a cloud CI/CD platform for those Expo apps, named Expo Application Services or <a href="https://expo.io/pricing">EAS</a>. As soon as users log into <a href="https://expo.io/">Expo</a>, depending on what projects they are a part of, the below is what they see.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*FSsT3VgbUP_YIhF-8UQYlg.png" /><figcaption>Our Expo dashboard when we log in and can see our builds on <a href="https://expo.io/">Expo</a></figcaption></figure><p>These services are built on top of the services that the SDK and CLI provide as well as being tightly connected to the Expo Go app which hosts and distributes apps in a method quicker than TestFlight or the PlayStore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41xkSLDzsUNFbaLHTssH3Q.png" /><figcaption>Summary of prices and services of EAS <a href="https://expo.io/pricing">Expo Application Services (EAS)</a></figcaption></figure><p>The three collective features that benefit developers of what is mentioned above in the EAS major features for their cloud deployment is cloud building, app signing and Over-the-air updates.</p><p>We are using <a href="https://www.bitrise.io/">Bitrise</a> to trigger builds at Transpire, and calling any of these builds for Store or Expo deployment is one line using the Expo CLI. And like it’s mentioned in the features, it handles the app signing on its platform automatically.</p><p>There are 3 types of deployments which are done through Expo CLI, publishing, building and uploading all on the Expo servers.</p><p>Uploading is not supported on iOS and needs to be done through their new service <a href="https://docs.expo.io/submit/ios/">EAS Submit</a>. We haven’t had time to set this up and decided to go for manual uploading on Android and iOS for our short PoC. This would be an investigation point if we can have all from OTA updates, building and uploading all automated from Bitrise. Going for manual publishing was not an issue since, due to over the air updates, apps only need to be published once or whenever native assets or native linked libraries change.</p><p>Building on the EAS servers uses credentials provided either by the CLI or on the Expo project to generate a build on their servers, ready to download when complete. Webhooks can be created to call when builds are created,</p><p><a href="https://docs.expo.io/distribution/webhooks/">Build Webhooks — Expo Documentation</a>. This is built alongside other builds and may be on hold. Checking the position of your build or the number of builds can be seen on their turtle site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NJ1KKVYNH_Vh72YFNy2ICQ.png" /><figcaption>Status of EAS build servers <a href="https://expo.io/turtle-status">Expo</a></figcaption></figure><p>Again this must be used because expo is a packaged system to abstract away native builds that require their system turtle. This is open source and can be done locally using their GitHub repo <a href="https://github.com/expo/turtle">expo/turtle</a>, also available as a CLI NPM package.</p><p>Expo publish which deploys javascript bundles to apps listening to their servers or to upload to Expo Go. Similar to the most popular service there is for React Native, <a href="https://microsoft.github.io/code-push/">Microsoft Code Push</a>, this allows us to create update alerts for users and to reply upon these OTA updates.</p><p>After experimenting with Expo publishing in Transpire, updates are instant to users and can also be specific to a specific release channel such as to develop or production. Apps build with specific release channel such as develop will only listen for new updates from that channel allowing a powerful multiple environments app deployment system. This system can be disabled, but by default, it is configured to check for updates on app fresh opens.</p><h3>Expo in Practice: T+ Market Place</h3><p>For a short PoC we were required to build, to take advantage of not having to set up anything relating to the native side in relation to icons/images as well as speeding up deployment, and with the benefit of OTA updates, we decided to stick with expo when initially developing this App.</p><h3>Automatic Updates and our CI/CD</h3><p>We wanted to make sure our app was always up to date and placed keeping the app at the latest version at a higher importance than breaking user experience. In this app, the user doesn’t submit any updates but instead only reads and consumes data. This data is also not deep and is simply a catalogue of offers.</p><p>Because of this making the app update when the user comes into the app at any time, we forced the user to update. We used the short snippet below to make this work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdCuf1cgo2C-4_9fF3lMiA.png" /></figure><p>When it came to our strategy, when compared to our <a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow">gitflow</a> structured branches, our Bitrise platform would trigger the specific types of builds with the specific environment on code changes.</p><p>Almost at all times these triggers trigger expo publishing OTA builds rather than physical IPA/APK bundle builds since older builds can get updated through the cloud and so are only built once every few months.</p><p>When develop branch detects a change, it pushes out a develop release channel build to Expo. When master branch detects a change, it pushes out a staging release channel build to Expo. When we’re comfortable with staging, we trigger a production release channel build off a release branch when we’re happy.</p><p>One weirdness we may update in the future is that ExpoGo only shows builds on the default release channel and so we send out default and develop release builds on development changes. We may in the future merge this into one and have the default as our development branch.</p><p>The amazing thing is that after a PR is merged, the update goes out to the app within 30 minutes, all automatically.</p><p>We still have not had a chance to make Testflight and Playstore build automated through the EAS CLI and will need to look into that in the future.</p><h3>Expo Constants</h3><p>To get information about the device so we can check accessibility status or for analytics, instead of requiring <a href="https://github.com/react-native-device-info/react-native-device-info">react-native-device-info</a>, we used Constants from <a href="https://docs.expo.io/versions/latest/sdk/constants/">expo-constants</a> to get this info.</p><p>We created a small utility function to get this information so we could get some of this useful information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HkqJRe__5CsgnIYy-Zc49Q.png" /></figure><h3>Will we use it in the future?</h3><p>There, of course, are times when we would need to not go with the expo, namely the primary reason, we need to access native modules that wouldn’t have otherwise been accessible in Expo. But again, for prototyping and rapid development, this may be rare, and for the sake of rapidly getting the project into clients hands, using expo and ejecting in the case of needing to will always be a recommendation of ours.</p><p>We will for the future need to investigate EAS CLI for apple publishing before we touch our next project.</p><p>Since we used it for a PoC, our decisions based on long term project health wasn’t an important one, but going forward we would need to consider the following things when looking into a new project.</p><ul><li>Will Expo support all the required native modules?</li><li>Do we need to integrate anything native?</li><li>Do we want to do the same thing again but with Microsoft Code Push?</li><li>Backwards compatibility and support (<a href="https://docs.expo.io/workflow/upgrading-expo-sdk-walkthrough/">Upgrading Expo SDK — Expo Documentation</a>)</li><li>Performance of EAS on bigger apps.</li><li>Can we trust Expo to handle support for updates for third party libraries such as Facebook/Firebase?</li><li>Can we reduce the size of the final app? (its very big for a basic hello world)</li><li>How easy will it be to eject from Expo?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a105ef0d5930" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/expo-a105ef0d5930">Expo</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Azure Cost Optimization Case Study]]></title>
            <link>https://medium.com/ciandt-techblog/an-azure-cost-optimization-case-study-27e5a985fa7e?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/27e5a985fa7e</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 07:02:53 GMT</pubDate>
            <atom:updated>2021-07-06T23:43:09.063Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/mehmet-altuntas-88a2b027/">Mehmet Altuntas</a>, Senior Azure Engineer, <a href="https://www.transpire.com/">Transpire</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*ESpW_pag6YlJHAtM0r2oRg.jpeg" /></figure><p>Designing a cloud solution should focus on generating incremental value in the early stages. Use the pay-as-you-go strategy for the architecture and invest in scaling out, rather than delivering a large investment first version. The cost calculator is a good start to estimate the initial cost and operational costs. The following next step would be to establish policies, budgets, and controls that set cost limits for the solution.</p><p>The following example is mainly focused on optimizing the resources in DEV and TEST environment for one of the projects in the Azure platform.</p><p>In our early stages, we have initially invested the existing resources plan types and pointed out whether the business requirements were being served with the bare minimum resources especially in a development environment.</p><p>What we found out was due to the lack of the governance and DevOps which led the users to create number of any type of resources and used them for the applications.</p><p>The following picture depicts the cost for the DEV environment:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/0*chJWjuADPS-LrqJg" /></figure><p>The following picture depicts the cost for the same environment after the Optimization:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/0*vkZBlK2txQP1I9Pj" /></figure><p>The cost difference is obviously substantial.</p><p>What we essentially accomplished in a short term was an efficient process of building and releasing multiple applications (DevOps) with a set of resources (Infrastructure as Code) in DEV and TEST environment which are leveraging Azure Active Directory and Key Vault to secure the communication between the applications.</p><h3>Principles</h3><p>The following principles are crucial to build and sustain a cost-effective workload while staying within a given budget:</p><ul><li>Keep within the cost constraints</li><li>Aim for scalable costs</li><li>Pay for consumption</li><li>Right resources, right size</li><li>Monitor and optimize</li></ul><p>We have also rectified the unused resources which do accumulate cost over the time. To prevent this issue is to apply policies from either a subscription or management level.</p><h3>Recommendations</h3><p>Some of the high level recommendations made for this project for the infrastructure team to put in place are listed below.</p><p><strong>Code Security</strong></p><ul><li>Leverage Azure Key Vault for DevOps and Applications securing the secrets</li></ul><p><strong>Governance — Security</strong></p><ul><li>Policy Enforcement: Application of Governance Patterns that could be applied on Subscription Model, Resource Grouping, Resource Tagging, Log and Reporting</li></ul><p><strong>Governance — Cost</strong></p><ul><li>Cost monitoring and reporting</li><li>Incremental improvement of the policy statements</li><li>Establish a budget</li><li>Choose right resources, right size</li></ul><p><strong>Governance — Backup/Recovery</strong></p><ul><li>Define and deploy Azure Recovery Service</li><li>Backup strategies — run on schedule</li></ul><p><strong>Governance — Subscription</strong></p><ul><li>Subscription topology should align with to the business</li></ul><p>Hope you find this useful to help you go about optimising cost for Azure projects. Happy savings!</p><h3>Credits and References:</h3><p><a href="https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/">https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/</a></p><p><a href="https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/govern/guides/complex/">https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/govern/guides/complex/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27e5a985fa7e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/an-azure-cost-optimization-case-study-27e5a985fa7e">An Azure Cost Optimization Case Study</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kotlin Multiplatform Mobile (KMM)]]></title>
            <link>https://medium.com/ciandt-techblog/kotlin-multiplatform-mobile-kmm-45db35fa65d1?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/45db35fa65d1</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[kmm]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Fri, 28 May 2021 00:34:29 GMT</pubDate>
            <atom:updated>2021-05-28T00:34:29.341Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/michaelhallorina/">Michael Hallorina</a>, QA, <a href="https://www.transpire.com/">Transpire</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HF1SItrYg8-E0Gc0vEqBLQ.jpeg" /></figure><h3>Tech Assessment — KMM from a QA perspective</h3><blockquote>Kotlin Multiplatform Mobile is an SDK that allows the use of the same business logic code in both iOS and Android applications. It was designed to help developers reuse their business logic between mobile platforms, whilst writing platform-specific code only where it’s necessary like to implement a native UI or when working with platform specific APIs.</blockquote><p>It uses multi-platform capabilities of Kotlin such as:</p><ul><li>Multiplatform Grade DSL</li><li>Kotlin/Native +</li><li>Kotlin/JVM +</li><li>Kotlin +</li></ul><p>It also uses tools and features designed to improve the experience of building mobile cross-platform applications such as:</p><ul><li>CocoaPods Integration +</li><li>Android Studio Plugin</li></ul><p>KMM can be integrated seamlessly, whether starting a new project or have a codebase that has grown over the years. Shared code written in Kotlin is compiled to JVM byte code with Kotlin/JVM (as per usual with Android Studio) and to native binaries for iOS with Kotlin/Native. Therefore KMM modules can be used like any other regular mobile library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*WWbf25NEYaHPxFwXZ-QVOA.png" /></figure><p><a href="https://medium.com/globant/kotlin-multiplatform-mobile-kmm-code-sharing-between-android-and-ios-9a9af66e2655"><em>Pic credit</em></a></p><p>There are no restrictions imposed in developing the UI as this is done natively for each platform.</p><p>You may decide to share only data layers, using popular libraries such as Ktor or SQLDelight.</p><h3>Tools Needed</h3><ul><li>Xcode</li><li>MacOS</li><li>Android Studio</li><li>Gradle</li><li>JDK</li></ul><p>The KMM Plugin for Android Studio offers integration with the iOS simulator and iOS device in Android Studio. It gives the ability to run and debug applications and Unit tests on iOS from Android Studio, without having to switch IDEs while working on the shared part of the code.</p><p>The project Wizard allows ready-to-run cross-platform mobile applications easily.</p><h3>Takeaways</h3><ul><li>Alternative to cross platform development</li><li>Useful if your app shares business logic and also want the UI to be customized natively or use platform specific APIs</li></ul><h3>How will it help QA?</h3><p>UI testing is still developed natively as the UI is developed respectively in Android Studio for Android or Xcode for iOS. Makes it easier to test and write same scenarios if both app have been developed using the same or similar elements and naming conventions. iOS code can be viewed in Android Studio without having to open Xcode.</p><h4><strong>Benefits</strong></h4><ul><li>Good for developers and writing Unit tests</li><li>More freedom in UI development native to the OS</li><li>Reduces app development time</li><li>Provides better access to APIs related to the OS</li></ul><h4><strong>Limitations</strong></h4><ul><li>Multithreading challenges, based on Coroutines tech with Kotlin which isn’t supported in Swift.</li><li>Not a Kotlin developer community</li></ul><h3>Similar Tools / Applications:</h3><p>KMM is an alternative to developing cross platform applications so it is similar to React-Native or Flutter but also directly using Android Studio and Xcode for the UI.</p><h3>Cost:</h3><p>Free to use — a plugin that can be downloaded and installed in Android Studio</p><h3>Instructions On How To Use:</h3><h4>Environment for KMM Development</h4><p>Android Studio 4.2 +<br>Xcode 11.3 +<br>Kotlin Plugin<br>Kotlin Multiplatform Mobile Plugin<br>Latest JDK</p><h4>Creating a KMM Application</h4><p>The wizard will create and set up all the dependences in Android Studio.<br>Create a New Project → Select KMM Application → Tick the checkbox to generate sample tests for project<br>Select Xcode build phases (packForXcode task) in iOS framework distribution.<br>Click Finish to set the project up.</p><h4>Running Application on Android</h4><p>In run configurations, select androidApp and then click Run.</p><h4>Running Application on iOS</h4><p>In Xcode Configure the Signing Capabilities and Select a team.<br>In Android Studio, choose iosApp in run configurations and then click Run.</p><h4>Running Unit Tests</h4><p><strong>iOS : </strong>Open the file iosTest.kt in shared/src/iosTest/Kotlin/com.example.appname.shared<br>Click Run icon in the gutter next to the test.</p><p><strong>Android: </strong>Open the file androidTest.kt in shared/src/androidTest/kotlin/com.example.appname.shared<br>Click Run icon in the gutter next to the test</p><h4>Adding KMM to An Existing Android Project</h4><p><strong>1. Decide Which Code To Make Cross-Platform<br></strong>Since the business logic will be the same for both iOS and Android, this will be the code that will be made cross-platform. The business logic is stored in the data folder in an Android application: com.application.androidapp.data</p><p><strong>2. Create A Shared Module For Cross-Platform Code<br></strong>A shared folder needs to be created which will later connect the existing Android app and future iOS app. KMM provides a special wizard for creating this module:</p><p>File → New → New Module<br>Select KMM Shared Module and name it ‘shared’<br>Tick the Generate packForXcode Gradle task checkbox<br>Click Finish</p><p><strong>3. Add A Dependency On The Shared Module To Android Application<br></strong>The shared module needs to connect to the Android app by moving the business logic there and also ensuring some dependencies and configurations are updated.<br>In the build.gradle.kts in the shared module, compileSdkVersion and minSdkVersion needs to be the same as build.gradle in the Android app module.<br>In the build.gradle of Android app module, add the following dependencies:</p><p>implementation project(‘:shared’)</p><p>Sync the gradle.</p><p><strong>4. Make The Business Logic Cross-Platform<br></strong>The business logic in the Android module needs to be moved to the Shared module. Drag the ‘data’ folder from:</p><p><em>app/src/main/com.application.androidapp directory</em></p><p>to the shared directory: <em>shared/src/commonMain.</em></p><p>Select to move the package and then approve the refactoring.</p><p><strong>5. Run The Cross-Platform App On Android To Ensure It Works</strong></p><h4>Making Cross Platform App Work On iOS</h4><p><strong>1. Create An iOS Project In Xcode</strong></p><p>File → New → Project<br>Select iOS App and Click Next<br>Put the same name as the App but with .ios at the end<br>Select the location which is in the directory that stores the cross platform application.</p><p><strong>2. Compile The Shared Module Into A Framework For The iOS Project</strong></p><p>In Android Studio type the following command in the Terminal:</p><p><em>./gradlew packForXcode</em></p><p>The generated framework will be stored in shared/build/xcode-frameworks directory</p><p><strong>3. Connect The Framework To The iOS Project</strong></p><p>In Xcode open the project settings<br>Under the General tab click the + under ‘Frameworks, Libraries, and Embedded Content’<br>Click Add Other then Add Files<br>Select the generated framework: shared/build/xcode-frameworks/shared.framework<br>Under the Build Settings tab under Search Paths, specify the Framework Search Paths:</p><p><em>$(SRCROOT)/../shared/build/xcode-frameworks</em></p><p><strong>4. Automate iOS Project Updates</strong></p><p>Configure automatic updates of the iOS project by avoiding recompiling framework after every change. Under Build Phases tab click + and add New Run Script Phase<br>Add the following script:</p><p><em>cd “$SRCROOT/..”</em></p><p><em>./gradlew :shared:packForXcode -PXCODE_CONFIGURATION=${CONFIGURATION}</em></p><p>Drag and move the Run Script phase before the Compile Sources phase</p><p><strong>5. Connect The Shared Module To The iOS Project</strong></p><p>In Xcode open the ContentView.swift file and import the shared module:</p><p><em>import shared</em></p><p><strong>6. Connect iOS application to Android Studio to run on a simulated or connected device</strong><br>In Advanced Studio, at the bottom of the gradle.properties file add the following line:</p><p><em>xcodeproj=iosApp/applicationName.xcodeproj</em></p><p>(replace application name with the name you have given)</p><h4>Adding UI Tests for Android</h4><p>In the Android module of a KMM app, UI tests can be implemented.</p><p>Test are created in the androidApp/src/androidTest/java folder</p><p>In build.gradle file of the Android module, the following dependencies need to be added:</p><p>In the defaultConfig section, the testInstrumentationRunner needs to be added:</p><p><em>testInstrumentationRunner “androidx.test.runner.AndroidJunitRunner”</em></p><p>Sync the gradle.</p><p>After creating a test, run the test to confirm the tests are working.</p><h4>Adding UI Tests for iOS</h4><p>UI tests can be configured when creating a KMM app, or when adding the iOS module to a KMM app if the “Add UI tests” box is ticked in the wizard.</p><p>If it wasn’t added, it can easily be configured as follows:</p><p>Open the iOS app in XCode<br>File → New → Target<br>Select iOS UI Testing Bundle<br>Click Finish</p><p>This will create a test class with some sample tests.</p><p><strong>Recording a Test</strong></p><p>At the top of the class add the following line:</p><p><em>var app: XCUIApplication!</em></p><p>Remove the tearDown function.</p><p>Inside the setUp function, replace contents with:</p><p><em>try super.setUpWithError()<br>continueAfterFailure — false<br>app = XCUIApplication()<br>app.launch()</em></p><p>Create a test function inside the class and inside the function press the Record button which will launch the app.<br>Interact with the app and when finished click the record button again to stop recording the test.<br>The function should have saved the interactions.<br>Edit and add assertions as necessary.</p><h3>Credits and References:</h3><p><a href="https://kotlinlang.org/docs/multiplatform.html">Multiplatform programming | Kotlin</a></p><p><a href="https://medium.com/globant/kotlin-multiplatform-mobile-kmm-code-sharing-between-android-and-ios-9a9af66e2655">https://medium.com/globant/kotlin-multiplatform-mobile-kmm-code-sharing-between-android-and-ios-9a9af66e2655</a></p><p><a href="https://medium.com/wantedly-engineering/different-approaches-in-consuming-kmm-modules-in-ios-7957c722b114">https://medium.com/wantedly-engineering/different-approaches-in-consuming-kmm-modules-in-ios-7957c722b114</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45db35fa65d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/kotlin-multiplatform-mobile-kmm-45db35fa65d1">Kotlin Multiplatform Mobile (KMM)</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MITM Attacks]]></title>
            <link>https://medium.com/ciandt-techblog/mitm-attacks-44e8c2b167f2?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/44e8c2b167f2</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[mitm]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Thu, 27 May 2021 06:28:09 GMT</pubDate>
            <atom:updated>2021-05-27T06:28:58.608Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Man in the middle attacks</strong></p><p><a href="https://www.linkedin.com/in/phyras-el-amin/">Phyras El Amin</a>, (Support Analyst, Masters of Cybersecurity), <a href="https://www.transpire.com/">Transpire</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xlhBJ0N-2i65uO8vgSQi_g.jpeg" /></figure><p>A Man in the middle attack (MITM) is one of the oldest ways of gaining access to unauthorised information. Hackers exploit a network or device by rerouting their connection to a secure site through their own servers controlled by them, and then re-establishing the link to a fake site. This works like a fake Bank Login page, but would send the data to the real site and allow a login, while harvesting the sensitive data.</p><p>These kinds of attacks are not very remote, as they are highly difficult to establish without being in close proximity to the target. A common method would be by using a DNS spoofer, and tricking a device and user into thinking they are connected to a site securely, but in reality are connected to a MITM with malicious intentions. The dangers of a MITM attack are even higher, as the introduction of SSL protocol makes users unaware of issues with web pages unless their browser gives them a big STOP header or page.</p><p><strong>This kind of attack is used in Government Information Exploitation, where rival states attempt to harvest details to access sensitive information</strong></p><p>Hackers using this exploitation is rare for a typical technology user, but for those in sensitive roles, it can be a big threat. MITM attacks have been used in the past by Russian KGB Agents as well as US CIA to attempt to collect information about impending attacks on their nations.</p><p>On a large scale, Stingray devices can be used to manipulate mobile networks (3G, 4G &amp; 5G) to collect information from a large number of users. Devices do not suspect they are connected to a malicious network that is routing their information, and when a Stingray device is used, the attack becomes automated and harvests all login credentials it can find and writes them to text files. These devices are readily available on the Darkweb and can be ordered by anyone.</p><p>Recommendations from a Cybersecurity student to protect yourself from such attacks would be:</p><p>1. Keep your browsers updated to the latest version</p><p>2. Avoid using Public Wi-Fi networks</p><p>3. Use a Keychain Manager (1Pass, LastPass, Remembear etc.)</p><p>4. Look at the little lock beside your URL and ensure you understand how you are connected</p><p>5. Never leave your sensitive pages logged in and change networks</p><p>6. Keep yourself informed, follow the Tech News, and read up about vulnerabilities in software</p><p>These attacks may one day become more prevalent, ensure you know the risks and how to protect yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44e8c2b167f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/mitm-attacks-44e8c2b167f2">MITM Attacks</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Social Engineering — Today’s Number 1 Option for Unauthorised Access]]></title>
            <link>https://medium.com/ciandt-techblog/social-engineering-todays-number-1-option-for-unauthorised-access-9401d845de27?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/9401d845de27</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[social-engineering]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Mon, 10 May 2021 06:30:28 GMT</pubDate>
            <atom:updated>2021-05-10T06:30:28.153Z</atom:updated>
            <content:encoded><![CDATA[<h3>Social Engineering — Today’s Number 1 Option for Unauthorised Access</h3><p><a href="https://www.linkedin.com/in/phyras-el-amin/">Phyras El Amin</a>, (Support Analyst, Masters of Cybersecurity), <a href="https://www.transpire.com/">Transpire</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3F8d6MLXz2BIuK2IlgQ_Ow.png" /></figure><p>“Without access to the Internet, your device becomes a paperweight…” That’s the general opinion these days. The way technology is progressing, we are relying on internet access more than ever, and it is an integral part of workplaces, especially since many work remotely.</p><p>With such a global push to move everything online, we tend to forget that there are dangers in this vast sea of digital 1’s and 0’s. In a commonly occurring example, a CEO of a massive tech firm has logged onto her computer, and opened her emails, finding an array of different business emails. However, one strikes as interesting, marked as high priority, the senders name being the manager of one of the companies she regularly liaises with for business transactions. Subject states; Cancellation of Project. The CEO is distraught and panics as she opens up the email which has nothing in it, except a link to a file named ‘new_contract.pdf’.</p><h3>“The CEO is distraught and panics as she opens up the email which has nothing in it, except a link to a file named ‘new_contract.pdf”</h3><p>Little did she know how far this went. This pdf file has a small change exploited within, the moment she clicks ‘open’, her entire company data is no longer safe. Hackers have come a long way from sitting behind computers and attempting to crack passwords. The BlackHat Hacking Community is far more advanced, and it is simple and easy for them to choose a target and begin exploiting through different methods now.</p><p>We have always been let down by authentication and password cracking on computers, but with new technology, passwords are encrypted with AES-128 by Google and Apple, setting a global standard for all companies to follow suit. Hackers simply cannot crack an AES-128 encrypted password with a brute force tool, this has become so difficult we would be providing supercomputers to even provide a hacker a chance to give the attack a try.</p><p>The hackers have adapted, and are targeting the weakest link, (it’s you…) Toolkits have been provided to the hacking community, they simply need to choose an option from a menu to create an attack, their machines do everything automatically, and it could even be used by a savvy 10 year old.</p><h3>“…they simply need to choose an option from a menu to create an attack, it’s all automated, and it could even be used by a savvy 10 year old”</h3><p>The only way for someone to be completely protected, would be to ensure they have no contact with a computer or device and AI was in charge of all files and data. The way we are progressing in the world means that we must be vigilant and be mindful of what links we click on, and what files we download, what pages we look at and what encryption we use. Otherwise we can fall victim to the BlackHat’s, lurking in the shadows, sending out emails that say you are related to a Nigerian Prince who wants to send you $100million that he suddenly feels entitled to give you.</p><p>If it sounds too good to be true… it probably is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9401d845de27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/social-engineering-todays-number-1-option-for-unauthorised-access-9401d845de27">Social Engineering — Today’s Number 1 Option for Unauthorised Access</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GatsbyJS & Auth0 Tech Assessment]]></title>
            <link>https://medium.com/ciandt-techblog/gatsbyjs-auth0-tech-assessment-6fa8c1aeb6a2?source=rss-92c296a8f221------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa8c1aeb6a2</guid>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[technical-analysis]]></category>
            <category><![CDATA[auth0]]></category>
            <category><![CDATA[gatsby]]></category>
            <dc:creator><![CDATA[CI&T Australia]]></dc:creator>
            <pubDate>Mon, 10 May 2021 01:13:18 GMT</pubDate>
            <atom:updated>2021-05-10T06:26:09.681Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.linkedin.com/in/evanamezcua/">Evan Amezcua</a>, Frontend Engineer, <a href="https://www.transpire.com/">Transpire</a></p><p>Gatsby and Auth0 has been in our Tech Radar for a while and recently we did a tech assessment to understand its benefits and shortcomings by using it to solve an actual problem. Sharing a condensed version of our experience here for you to read.</p><h3>Protec the Spec — Transpire in-house apis</h3><p>Created with Gatsby, auth with Auth0</p><h3>Tech to test:</h3><p>GatsbyJS and Auth0</p><h3>Problem to solve:</h3><p>At Transpire, we have multiple projects that the team is currently working on. Most projects have an API being developed and documented, but that API spec is usually isolated in the projects repository. Sharing this documentation with team members can be difficult, and it’s not always easy to find. This documentation also isn’t always something that should be public, and needs to be housed in a way that only people who are allowed can access it.</p><p>As part of this tech assessment we thought of having all the api specs in one place, in a single project hosted in an S3 bucket, and deployed with Cloudfront. Code is hosted on internal Bitbucket repo. Api specs are *.yaml, located in public/specs/ directory.</p><h3>Learnings</h3><h3>Benefits:</h3><p><strong>Gatsby:</strong></p><ul><li>Performance! It’s so fast. (Noted to be 2–3 times faster than similar sites in vanilla React)</li><li>Documentation is super robust, well outlined with good examples. <a href="https://www.gatsbyjs.com/docs/">https://www.gatsbyjs.com/docs/</a> This has basic how-to guides, but also specific guides for use with different CMSs or tech.</li><li>Integrations — many popular techs have bootstrapped project templates, integrations, etc (typescript!!) called Starter Libraries. This might be for a blog, a simple portfolio, or a CMS such as Netlify or WordPress.</li><li>There is also many nice-to-have features like react-router, lazy loading images, code splitting, PWA support out of the box. These can be tough to implement in to an existing project, so if performance is a key driver, Gatsby should be considered.</li></ul><p><strong>Auth0:</strong></p><ul><li>Quick and easy setup, and can be run entirely on the front end — I’m a front end dev with minimal back end/auth experience, and had it working within a few hours. This is a huge benefit in my eyes, as it would allow for a simple auth layer to be added to a project without needing someone with Cognito experience or similar.</li><li>JWT support in serverless applications out of the box with no cost.</li><li>Easy dashboard that can be used to edit settings even for a non-dev user. This may be useful for setting roles and permissions as a PM, or allowing clients to have visibility over private docs. These permissions are then passed as an object in to the application after the user is authenticated, and can be used programatically to show or hide content as needed.</li><li>Create rules in JS in-browser to edit permissions on the fly as users log in/out — this means that permissions do not need to be set to individual users, but can be created on an ad-hoc basis as they join if the necessary rules have been created.</li><li>Free with up to 7,000 active users and unlimited logins — this is plenty for a small scale project.</li></ul><h3>Shortcomings:</h3><p><strong>Gatsby:</strong></p><ul><li>May be unnecessarily complex for a very simple project such as this — developers will need to be familiar with GraphQL to best utilise Gatsby.</li><li>Regular CRA React app is faster to develop -&gt; deploy a simple project if you’re familiar with the process.</li></ul><p><strong>Auth0:</strong></p><ul><li>Additional price to factor in, and is considerably more costly than AWS Cognito</li><li>Community support appears to be lacking for free tier customers, but dev level support starts at $13/month.</li><li>$23/mo for: Up to 50,000 External MAU, Unlimited Social Connections, Custom Domains, Role Management, Up to 5 Rules but only 100 active users monthly.</li><li>Cost scales exponentially, roughly $114/mo for 5000 active users, or $1000/mo for a developer pro account. Anything over 50k monthly active users requires contacting Auth0 for an enterprise solution.</li></ul><h3>What is still to do?</h3><ul><li>A strategy for publishing api specs to the code repo with as little friction as possible — I’d like to avoid needing to cherry pick commits, or force people to push their code to two places. This solution will only be useful if the spec sheets reflect the most up-to-date version of the API, and must be a source or truth.</li><li>Deployment pipeline that will allow the resources to be up to date. There is still an ongoing discussion on the best approach to solve this problem.</li><li>A way to port this app so that it can be easily used for a single project</li></ul><h3>Did this meet the needs &amp; solve the problem?</h3><ul><li>Yes, I believe that it did. However, for a project of this size I believe using Gatsby would be an unnecessary overhead to introduce. I think that Auth0 was the stand out technology from this assessment, and I can see it having a place in a number of small to medium sized projects that need authentication functionality.</li></ul><h3>Any other alternatives:</h3><ul><li>Next.js is probably the biggest and most common alternative to Gatsby, and as it’s more mature/established it may mean that finding experts comes easier.</li><li>AWS Cognito for auth, while more complicated, is still tied in to the AWS suite, making data analytics easier. Cognito is also exponentially cheaper, however this comes as the cost of complexity.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa8c1aeb6a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ciandt-techblog/gatsbyjs-auth0-tech-assessment-6fa8c1aeb6a2">GatsbyJS &amp; Auth0 Tech Assessment</a> was originally published in <a href="https://medium.com/ciandt-techblog">CI&amp;T Australia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>