Skip to main content

107 posts tagged with "iOS"

View All Tags

Integrating Hasura and Implementing GraphQL in Swift-Based iOS Apps Using Apollo

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

Building robust and efficient iOS applications often involves integrating powerful backend services. Hasura, a real-time GraphQL engine, provides a convenient way to connect and interact with databases, enabling seamless integration between your iOS app and your backend.

In this tutorial, we will explore how to integrate Hasura and use GraphQL in Swift-based iOS apps. We will cover all CRUD operations (Create, Read, Update, Delete), as well as subscribing and unsubscribing to real-time updates.

Prerequisites​

To follow this tutorial, you should have the following:

  • Xcode installed on your machine

  • Basic knowledge of Swift programming

  • Hasura GraphQL endpoint and access to a PostgreSQL database

1. Set Up Hasura and Database​

Before we dive into coding, let's set up Hasura and Database:

1.1 Install Hasura CLI​

Open a terminal and run the following command:

curl -L https://github.com/hasura/graphql-engine/raw/stable/cli/get.sh | bash

1.2 Initialize Hasura project​

Navigate to your project directory and run:

hasura init hasura-app

1.3 Configure Hasura​

Modify the config.yaml file generated in the previous step to specify your database connection details.

1.4 Apply migrations​

Apply the initial migration to create the required tables and schema. Run the following command:

hasura migrate apply

1.5 Start the Hasura server​

Run the following command:

hasura server start

2. Set Up the iOS Project​

Now let's set up our iOS project and integrate the required dependencies:

  • Create a new Swift-based iOS project in Xcode.

  • Install Apollo GraphQL Client: Use CocoaPods or Swift Package Manager to install the Apollo iOS library. Add the following line to your Podfile and run pod install:

pod 'Apollo'
  • Create an ApolloClient instance: Open the project's AppDelegate.swift file and import the Apollo framework. Configure and create an instance of ApolloClient with your Hasura GraphQL endpoint.
import Apollo

// Add the following code in your AppDelegate.swift file
let apollo = ApolloClient(url: URL(string: "https://your-hasura-endpoint")!)

3. Perform CRUD Operations with GraphQL​

Now we'll demonstrate how to perform CRUD operations using GraphQL in your Swift-based iOS app:

3.1 Define GraphQL queries and mutations​

In your project, create a new file called GraphQL.swift and define the GraphQL queries and mutations you'll be using. For example:

import Foundation

struct GraphQL {
static let getAllUsers = """
query GetAllUsers {
users {
id
name
email
}
}
"""
static let createUser = """
mutation CreateUser($name: String!, $email: String!) {
insert_users_one(object: {name: $name, email: $email}) {
id
name
email
}
}
"""
static let updateUser = """
mutation UpdateUser($id: Int!, $name: String, $email: String) {
update_users_by_pk(pk_columns: {id: $id}, _set: {name: $name, email: $email}) {
id
name
email
}
}
"""
static let deleteUser = """
mutation DeleteUser($id: Int!) {
delete_users_by_pk(id: $id) {
id
name
email
}
}
"""
}

3.2 Fetch data using GraphQL queries​

In your view controller, import the Apollo framework and make use of the ApolloClient to execute queries. For example:

import Apollo

class ViewController: UIViewController {
override func viewDidLoad() {
super.viewDidLoad()

apollo.fetch(query: GetAllUsersQuery()) {
result in
switch result {
case .success(let graphQLResult):
// Handle the result
if let users = graphQLResult.data?.users {
// Process the users data
}

case .failure(let error):
// Handle the error
print("Error fetching users: \(error)")
}
}
}
}

3.3 Perform mutations for creating/updating/deleting data​

Use ApolloClient to execute mutations. For example:

// Create a user
apollo.perform(mutation: CreateUserMutation(name: "John", email: "john@example.com")) { result in
switch result {
case .success(let graphQLResult):
// Handle the result
if let user = graphQLResult.data?.insert_users_one {
// Process the newly created user
}

case .failure(let error):
// Handle the error
print("Error creating user: \(error)")
}
}

// Update a user
apollo.perform(mutation: UpdateUserMutation(id: 1, name: "Updated Name", email: "updated@example.com")) { result in
switch result {
case .success(let graphQLResult):
// Handle the result
if let updatedUser = graphQLResult.data?.update_users_by_pk {
// Process the updated user data
}

case .failure(let error):
// Handle the error
print("Error updating user: \(error)")
}
}

// Delete a user
apollo.perform(mutation: DeleteUserMutation(id: 1)) { result in
switch result {
case .success(let graphQLResult):
// Handle the result
if let deletedUser = graphQLResult.data?.delete_users_by_pk {
// Process the deleted user data
}

case .failure(let error):
// Handle the error
print("Error deleting user: \(error)")
}
}

​

4. Subscribe and Unsubscribe to Real-Time Updates​

Hasura allows you to subscribe to real-time updates for specific data changes. Let's see how to do that in your iOS app:

4.1 Define a subscription​

Add the subscription definition to your GraphQL.swift file. For example:

static let userAddedSubscription = """
subscription UserAdded {
users {
id
name
email
}
}
"""

4.2 Subscribe to updates​

In your view controller, use ApolloClient to subscribe to the updates. For example:

swiftCopy code
let subscription = apollo.subscribe(subscription: UserAddedSubscription()) { result in
switch result {
case .success(let graphQLResult):
// Handle the real-time update
if let user = graphQLResult.data?.users {
// Process the newly added user
}

case .failure(let error):
// Handle the error
print("Error subscribing to user additions: \(error)")
}
}

4.3 Unsubscribe from updates​

When you no longer need to receive updates, you can unsubscribe by calling the cancel method on the subscription object.

subscription.cancel()

Conclusion​

In this tutorial, we learned how to integrate Hasura and use GraphQL in Swift-based iOS apps. We covered the implementation of CRUD operations (Create, Read, Update, Delete), as well as subscribing and unsubscribing to real-time updates.

By leveraging the power of Hasura and GraphQL, you can build responsive and efficient iOS apps that seamlessly connect with your backend services.

Happy coding!

Maximizing Efficiency in iOS App Testing with BrowserStack and Appxiom

Published: · Last updated: · 4 min read
Appxiom Team
Mobile App Performance Experts

In today's rapidly evolving mobile app ecosystem, delivering a seamless user experience is crucial for success. To ensure high-quality iOS app performance, it's essential to have robust testing tools and frameworks in place.

This blog post explores the integration of BrowserStack and Appxiom, two powerful tools, to maximize the efficiency of iOS app testing. By leveraging their combined features, developers can identify and resolve performance issues, bugs, and other potential pitfalls more effectively.

Understanding BrowserStack​

BrowserStack is a comprehensive testing platform that provides developers with a cloud-based infrastructure to test their applications on a wide range of real iOS devices. It offers an extensive device lab that includes the latest iPhone and iPad models, enabling thorough compatibility testing across various screen sizes, resolutions, and iOS versions. By utilizing BrowserStack, developers can ensure their iOS apps work seamlessly on different devices, reducing the risk of device-specific issues.

Introducing Appxiom​

Appxiom is a lightweight tool available as an Android SDK and iOS framework. It offers valuable insights into the performance of iOS apps during both the QA and live phases. Appxiom helps detect performance issues such as memory leaks, abnormal memory usage, frame rate problems, app hangs, network call-related issues, function failures, and more. It generates detailed bug reports, including relevant data points that aid developers in reproducing and resolving bugs efficiently.

Integration Process​

To maximize the efficiency of iOS app testing, follow these steps to integrate BrowserStack and Appxiom:

Step 1: Setting up BrowserStack​

  • Create a BrowserStack account at https://www.browserstack.com/.

  • Familiarize yourself with BrowserStack's documentation and capabilities.

  • Install the required dependencies and configure your testing environment.

Step 2: Integrating Appxiom​

  • Register with Appxiom using the 'Get Started' button in https://appxiom.com and login to dashboard.

  • Use "Add App" to link iOS application to Appxiom.

  • Integrate Appxiom framework to your application as explained in https://docs.appxiom.com.

  • Test your integration.

Step 3: Running Tests on BrowserStack​

  • Utilize BrowserStack's extensive device lab to select the desired iOS devices for testing.

  • Configure your testing environment to run your iOS app on the chosen devices.

  • Implement test scripts or utilize existing test frameworks to automate your tests.

  • Execute tests on BrowserStack and observe the results.

Step 4: Analyzing Appxiom Reports​

  • After running tests on BrowserStack, login to Appxiom dashboard.

  • Identify any performance issues, bugs, or abnormalities observed during the test.

  • Leverage Appxiom' detailed bug reports and data points to gain deeper insights into the detected issues.

  • Use the information provided by Appxiom to reproduce and fix bugs efficiently.

Benefits of Using BrowserStack and Appxiom Together for iOS App Testing​

By combining BrowserStack and Appxiom, iOS app developers can experience the following benefits:

a) Enhanced Device Coverage​

BrowserStack's device lab offers access to a wide range of real iOS devices, ensuring comprehensive compatibility testing. This reduces the risk of device-specific issues going unnoticed.

b) Efficient Bug Identification​

Appxiom' advanced monitoring capabilities help detect performance issues and bugs in iOS apps. It provides detailed bug reports and data points, making it easier for developers to identify, reproduce, and fix issues quickly.

c) Reproducible Testing Environment​

BrowserStack's cloud-based infrastructure ensures a consistent testing environment across multiple devices. This allows developers to replicate and verify bugs more accurately.

d) Streamlined Bug Resolution​

By leveraging Appxiom' detailed bug reports, developers can understand the root cause of issues quickly. This accelerates the bug resolution process, leading to faster app improvements.

e) Time and Cost Savings​

The integration of BrowserStack and Appxiom optimizes the iOS app testing workflow, reducing the time and effort required for testing and bug fixing. This ultimately leads to cost savings and improved time-to-market.

Conclusion​

Using BrowserStack and Appxiom together offers a powerful combination of testing capabilities for iOS app development. By leveraging BrowserStack's extensive device lab and Appxiom' performance monitoring and bug detection features, developers can streamline their testing process, identify issues efficiently, and deliver high-quality iOS apps to users. Integrating these tools is a valuable strategy to maximize the efficiency of iOS app testing and ensure a seamless user experience in today's competitive mobile landscape.

Happy testing!

How to Integrate Firestore with Swift and How to Use It in iOS Apps

Published: · Last updated: · 3 min read
Appxiom Team
Mobile App Performance Experts

Firebase Firestore is a cloud-based NoSQL database that allows you to store and retrieve data in real time. It is an excellent choice for iOS apps due to its ease of use, scalability, and security.

In this blog post, we will guide you through the process of integrating Firestore with Swift and demonstrate how to leverage its features in iOS development.

Adding Firebase to Your iOS Project​

To begin, you need to add Firebase to your iOS project. Follow the instructions provided in the Firebase documentation (https://firebase.google.com/docs/ios/setup) to complete this step.

Once you have successfully added Firebase to your project, you must import the FirebaseFirestoreSwift framework. To do this, add the following line to your Podfile:

pod 'FirebaseFirestoreSwift'

Mapping Firestore Data to Swift Types​

Firestore data is stored in documents, which are essentially JSON objects. You can map Firestore documents to Swift types by utilizing the Codable protocol.

To map a Firestore document to a Swift type, your type declaration should conform to Codable. Add the following two lines to your type declaration:

import Codable

@objc(MyDocument)struct MyDocument: Codable {
// ...
}

By adopting the Codable protocol, you gain access to a range of methods for encoding and decoding JSON objects. These methods will facilitate the reading and writing of data to Firestore.

Reading and Writing Data to Firestore​

After successfully mapping your Firestore data to Swift types, you can commence reading and writing data to Firestore.

To read data from Firestore, utilize the DocumentReference class. This class offers several methods for obtaining, setting, and deleting data from Firestore documents.

For instance, the following code retrieves data from a Firestore document:

let document = Firestore.firestore().document("my-document")
let data = try document.data(as: MyDocument.self)

To write data to Firestore, make use of the setData() method on the DocumentReference class. This method accepts a dictionary of key-value pairs as its argument.

For example, the following code writes data to a Firestore document:

let document = Firestore.firestore().document("my-document")
document.setData(["name": "Robin", "age": 30])

Using Firestore in a Real-Time App​

Firestore is a real-time database, meaning that any changes made to the data are instantly reflected across all connected clients. This real-time capability makes Firestore an ideal choice for developing real-time apps.

To incorporate Firestore into a real-time app, employ the Listener class. This class provides a mechanism for listening to changes in Firestore data.

For instance, the following code sets up a listener to monitor changes in a Firestore document:

let document = Firestore.firestore().document("my-document")
let listener = document.addSnapshotListener { snapshot, error inif let error = error {
// Handle the error
} else {
// Update the UI with new data
}
}

Conclusion​

In this blog post, we explored the process of integrating Firestore with Swift and demonstrated its utilization in iOS development.

We hope this blog post has provided you with a solid foundation for working with Firestore in Swift.

Happy Coding!

Guide for Integrating GraphQL with Flutter Using Hasura

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

In today's mobile app development landscape, building data-driven applications is a common requirement. To efficiently handle data fetching and manipulation, it's crucial to have a robust API layer that simplifies the communication between the frontend and backend.

GraphQL, a query language for APIs, and Hasura, an open-source GraphQL engine, offer a powerful combination for building data-driven Flutter apps. In this blog post, we will explore how to integrate GraphQL with Flutter using Hasura and leverage its features to create efficient and scalable apps.

Prerequisites​

To follow along with this tutorial, you should have the following prerequisites:

  • Basic knowledge of Flutter and Dart.

  • Flutter SDK installed on your machine.

  • An existing Flutter project or create a new one using flutter create my_flutter_app.

Set up Hasura GraphQL Engine​

Before integrating GraphQL with Flutter, we need to set up the Hasura GraphQL Engine to expose our data through a GraphQL API. Here's a high-level overview of the setup process:

1. Install Hasura GraphQL Engine:​

  • Option 1: Using Docker:

Install Docker on your machine if you haven't already.

  • Pull the Hasura GraphQL Engine Docker image using the command: docker pull hasura/graphql-engine.

  • Start the Hasura GraphQL Engine container: docker run -d -p 8080:8080 hasura/graphql-engine.

  • Option 2: Using Hasura Cloud:

Visit the Hasura Cloud website (https://hasura.io/cloud) and sign up for an account.

  • Create a new project and follow the setup instructions provided.

2. Set up Hasura Console​

  • Access the Hasura Console by visiting http://localhost:8080 or your Hasura Cloud project URL.

  • Authenticate with the provided credentials (default is admin:admin).

  • Create a new table or use an existing one to define your data schema.

3. Define GraphQL Schema​

Use the Hasura Console to define your GraphQL schema by auto-generating it from an existing database schema or manually defining it using the GraphQL SDL (Schema Definition Language).

4. Explore GraphQL API​

Once the schema is defined, you can explore the GraphQL API by executing queries, mutations, and subscriptions in the Hasura Console.

Congratulations! You have successfully set up the Hasura GraphQL Engine. Now, let's integrate it into our Flutter app.

Add Dependencies​

To use GraphQL in Flutter, we need to add the necessary dependencies to our pubspec.yaml file. Open the file and add the following lines:

dependencies:flutter:sdk: fluttergraphql_flutter: ^5.1.2

Save the file and run flutter pub get to fetch the dependencies.

Create GraphQL Client​

To interact with the Hasura GraphQL API, we need to create a GraphQL client in our Flutter app. Create a new file, graphql_client.dart, and add the following code:

import 'package:graphql_flutter/graphql_flutter.dart';

class GraphQLService {
static final HttpLink httpLink = HttpLink('http://localhost:8080/v1/graphql');

static final GraphQLClient client = GraphQLClient(
link: httpLink,
cache: GraphQLCache(),
);
}

In the above code, we define an HTTP link to connect to our Hasura GraphQL API endpoint. You may need to update the URL if you are using Hasura Cloud or a different port. We then create a GraphQL client using the GraphQLClient class from the graphql_flutter package.

Query Data from Hasura​

Now, let's fetch data from the Hasura GraphQL API using our GraphQL client. Update your main Flutter widget (main.dart) with the following code:

import 'package:flutter/material.dart';
import 'package:graphql_flutter/graphql_flutter.dart';

import 'graphql_client.dart';

void main() {
runApp(MyApp());
}

class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return GraphQLProvider(
client: GraphQLService.client,
child: MaterialApp(
title: 'Flutter GraphQL Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: MyHomePage(),
),
);
}
}

class MyHomePage extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text('GraphQL Demo'),
),
body: Query(
options: QueryOptions(
document: gql('YOUR_GRAPHQL_QUERY_HERE'),
),
builder: (QueryResult result, {VoidCallback? refetch}) {
if (result.hasException) {
return Text(result.exception.toString());
}

if (result.isLoading) {
return CircularProgressIndicator();
}

// Process the result.data object and display the data in your UI
// ...

return Container();
},
),
);
}
}

In the above code, we wrap our Flutter app with the GraphQLProvider widget, which provides the GraphQL client to all descendant widgets. Inside the MyHomePage widget, we use the Query widget from graphql_flutter to execute a GraphQL query. Replace 'YOUR_GRAPHQL_QUERY_HERE' with the actual GraphQL query you want to execute.

Display Data in the UI​

Inside the builder method of the Query widget, we can access the query result using the result parameter. Process the result.data object to extract the required data and display it in your UI. You can use any Flutter widget to display the data, such as Text, ListView, or custom widgets.

Congratulations! You have successfully integrated GraphQL with Flutter using Hasura. You can now fetch and display data from your Hasura GraphQL API in your Flutter app.

Conclusion​

In this blog post, we explored how to integrate GraphQL with Flutter using Hasura. We set up the Hasura GraphQL Engine, created a GraphQL client in Flutter, queried data from the Hasura GraphQL API, and displayed it in the UI.

By leveraging the power of GraphQL and the simplicity of Hasura, you can build efficient and scalable data-driven apps with Flutter.

Remember to handle error scenarios, mutations, and subscriptions based on your app requirements. Explore the graphql_flutter package documentation for more advanced usage and features.

Happy coding!

Guide to Implement Continuous Integration (CI) and Continuous Delivery (CD) for iOS Apps

Published: · Last updated: · 4 min read
Appxiom Team
Mobile App Performance Experts

In today's fast-paced software development world, it is essential to adopt efficient practices that enable continuous integration (CI) and continuous delivery (CD) to ensure the smooth and seamless development of iOS apps. CI/CD workflows automate the process of building, testing, and delivering software, allowing developers to iterate quickly and deliver high-quality applications.

This blog post will provide a high-level guide on implementing CI/CD for iOS apps, outlining the key concepts, tools, and best practices involved.

Understanding Continuous Integration and Continuous Delivery​

Continuous Integration (CI) is a development practice that involves integrating code changes from multiple developers into a shared repository. It ensures that the changes are tested automatically and merged regularly, reducing integration issues and catching bugs early. Continuous Delivery (CD) extends CI by automating the release process, enabling rapid and frequent deployment of software updates.

Setting Up a CI/CD Environment​

To implement CI/CD for iOS apps, you need to establish a dedicated CI/CD environment. This environment typically consists of a version control system, a build server, testing frameworks, and deployment tools. Consider using a cloud-based solution for scalability and ease of management.

Choosing a CI/CD Tool​

Several CI/CD tools support iOS app development, including Jenkins, Travis CI, CircleCI, and Bitrise. Evaluate each tool based on factors like ease of setup, integration with version control systems, support for automated testing, scalability, and pricing.

Creating a Build Pipeline​

A typical CI/CD workflow involves a series of steps in a build pipeline.

Here are the key components to consider:

1. Version Control and Branching Strategy​

Use a version control system (e.g., Git) and adopt an appropriate branching strategy, such as GitFlow. This allows for effective collaboration, isolation of feature development, and bug fixing.

2. Build Configuration​

Create a build configuration file (e.g., Xcode project or Fastlane) to define build settings, code signing details, and dependencies. Automate the build process to ensure consistency across environments.

3. Automated Testing​

Leverage testing frameworks like XCTest or third-party tools such as EarlGrey or Quick/Nimble to create automated tests. Integrate these tests into your CI/CD pipeline to detect regressions and ensure the stability of your app.

4. Code Signing and Provisioning Profiles​

Manage code signing identities and provisioning profiles for different environments (e.g., development, staging, and production). Use a secure and automated approach, such as Fastlane match or App Store Connect API, to simplify the code signing process.

Implementing Continuous Delivery​

To achieve continuous delivery, automate the deployment process and streamline the release cycle. Consider the following aspects:

1. Deployment Automation​

Automate the app deployment process using tools like Fastlane or custom scripts. This includes activities such as archiving the app, generating release notes, managing metadata, and uploading to distribution platforms.

2. App Store Release Process​

Automate the release process to the App Store by leveraging tools like Fastlane's deliver or the App Store Connect API. This allows you to upload your app, submit it for review, and manage versioning and release notes seamlessly.

Monitoring and Analytics​

Integrate monitoring and analytics tools, such as Firebase and Appxiom, into your CI/CD pipeline to track the performance and usage of your app. This helps in identifying issues and making data-driven decisions for future improvements.

Best Practices for CI/CD in iOS Apps​

  • Ensure a comprehensive suite of automated tests to validate your app's functionality.

  • Use version control branches effectively to isolate features and bug fixes.

  • Store sensitive information (e.g., API keys, passwords) securely using environment variables or encrypted files.

  • Regularly update your CI/CD tools, dependencies, and frameworks to benefit from the latest features and security patches.

  • Implement a feedback loop to collect user feedback and iterate on your app's features and performance.

Conclusion​

Implementing CI/CD for iOS apps streamlines the development, testing, and deployment processes, enabling faster iterations and high-quality releases. By automating tasks and integrating various tools, developers can focus more on building great apps while ensuring efficiency and reliability. Embracing CI/CD practices empowers developers to deliver feature-rich applications to users in a timely manner, while maintaining the highest standards of quality and performance.

Using flutter_native_image Plugin to Do Image Processing in Flutter Apps

Published: · Last updated: · 3 min read
Appxiom Team
Mobile App Performance Experts

Image processing plays a crucial role in many mobile applications, enabling developers to enhance, manipulate, and optimize images according to specific requirements. Flutter, a cross-platform framework, provides numerous tools and packages to handle image processing tasks effectively.

In this blog post, we will explore the flutter_native_image package, which offers advanced image processing capabilities in Flutter applications.

What is flutter_native_image?​

flutter_native_image is a powerful Flutter package that allows developers to perform image processing operations using native code. It leverages the native image processing capabilities available on both Android and iOS platforms, resulting in faster and more efficient image operations.

Installation​

To begin using flutter_native_image in your Flutter project, add it as a dependency in your pubspec.yaml file:

dependencies:flutter_native_image: ^1.0.6

After adding the dependency, run flutter pub get to fetch the package and its dependencies.

Using flutter_native_image​

The flutter_native_image package provides various image processing operations, including resizing, cropping, rotating, compressing, and more. Let's explore some of these operations with code samples.

1. Resizing Images​

Resizing images is a common requirement in mobile applications. The flutter_native_image package makes it straightforward to resize images in Flutter.

Here's an example of resizing an image to a specific width and height:

import 'package:flutter_native_image/flutter_native_image.dart';

Future<void> resizeImage() async {
String imagePath = 'path/to/image.jpg';
ImageProperties properties = await FlutterNativeImage.getImageProperties(imagePath);
File resizedImage = await FlutterNativeImage.resizeImage(
imagePath: imagePath,
targetWidth: 500,
targetHeight: 500,
);
// Process the resized image further or display it in your Flutter UI.
}

2. Compressing Images​

Image compression is essential to reduce the file size of images without significant loss of quality. The flutter_native_image package allows you to compress images efficiently.

Here's an example:

import 'package:flutter_native_image/flutter_native_image.dart';

Future<void> compressImage() async {
String imagePath = 'path/to/image.jpg';
File compressedImage = await FlutterNativeImage.compressImage(
imagePath,
quality: 80,
percentage: 70,
);
// Process the compressed image further or display it in your Flutter UI.
}

3. Rotating Images​

In some cases, you may need to rotate images based on user interactions or other requirements. The flutter_native_image package simplifies image rotation tasks.

Here's an example:

import 'package:flutter_native_image/flutter_native_image.dart';

Future<void> rotateImage() async {
String imagePath = 'path/to/image.jpg';
File rotatedImage = await FlutterNativeImage.rotateImage(
imagePath: imagePath,
degree: 90,
);
// Process the rotated image further or display it in your Flutter UI.
}

4. Cropping Images​

Cropping images allows you to extract specific regions of interest from an image. The flutter_native_image package enables easy cropping of images. Here's an example:

import 'package:flutter_native_image/flutter_native_image.dart';

Future<void> cropImage() async {
String imagePath = 'path/to/image.jpg';
File croppedImage = await FlutterNativeImage.cropImage(
imagePath: imagePath,
originX: 100,
originY: 100,
width: 300,
height: 300,
);
// Process the cropped image further or display it in your Flutter UI.
}

Conclusion​

Image processing is a fundamental aspect of many Flutter applications, and the flutter_native_image package simplifies the process by leveraging the native image processing capabilities of Android and iOS platforms.

In this blog post, we explored some of the key image processing operations, including resizing, compressing, rotating, and cropping images using flutter_native_image. By incorporating these operations into your Flutter project, you can enhance the visual experience, optimize image sizes, and meet specific application requirements efficiently.

Remember to check the official flutter_native_image package documentation for more information and additional functionalities.

Happy coding!

How to Use Generics in Swift

Published: · Last updated: · 4 min read
Appxiom Team
Mobile App Performance Experts

Swift, Apple's modern programming language, offers a powerful feature called generics that greatly enhances code reusability, efficiency, and safety.

In this blog post, we will dive deep into generics and explore how they can be leveraged in iOS development. We will provide an overview of generics, demonstrate their usage with code examples, and highlight the benefits they bring to your iOS projects.

What are Generics?​

Generics in Swift enable you to write flexible and reusable code that can work with different types of data. By using generics, you can create functions, classes, and structures that operate uniformly on a variety of types, avoiding code duplication and increasing maintainability.

How to Use Generics in Swift?​

To utilize generics, you need to define a generic type or function. Let's start by examining generic types in Swift.

Generic Types:​

A generic type can represent any specific type, allowing for maximum flexibility. Here's an example of a generic class called Stack that can store and manipulate a stack of elements of any type:

class Stack<T> {
var items = [T]()

func push(item: T) {
items.append(item)
}

func pop() -> T? {
return items.popLast()
}
}

In the code snippet above, we define a Stack class with a generic type parameter T. This parameter acts as a placeholder for any type that will be used with the Stack instance. The push function allows us to add elements to the stack, while the pop function removes and returns the topmost element from the stack.

Generic Functions:​

Similarly, you can define generic functions that can work with different types. Let's look at an example of a generic function for swapping two values:

func swap<T>(_ a: inout T, _ b: inout T) {
let temp = a
a = b
b = temp
}

In this code snippet, the swap function is defined with a type parameter T using the placeholder <T>. The function takes in two parameters of the same type (a and b) and swaps their values using a temporary variable.

Advantages of Using Generics in iOS Development​

Generics can be immensely beneficial in iOS development, offering increased code reuse, improved efficiency, and enhanced safety. Let's explore some practical use cases for leveraging generics in your iOS projects.

1. Reusable Code:​

Generics enable you to create reusable code that can work with different data types. For example, consider a generic function that sorts an array of any type:

func sortArray<T: Comparable>(_ array: [T]) -> [T] {
return array.sorted()
}

In this example, the sortArray function takes in an array of type T, constrained by the Comparable protocol to ensure elements can be compared. The function then returns the sorted array.

By using this generic function, you can sort arrays of integers, strings, or any other type that conforms to the Comparable protocol. This reusability saves you from writing separate sorting functions for each specific type.

2. Enhanced Efficiency:​

Generics can also improve the efficiency of your code by eliminating the need for type casting. Consider a generic function that compares two values without explicitly specifying their types:

func compare<T: Equatable>(_ a: T, _ b: T) -> Bool {
return a == b
}

In this case, the compare function takes two parameters of type T, constrained by the Equatable protocol, which ensures that values can be equated using the == operator. The function then compares the two values and returns a Boolean result.

By using this generic function, you can compare values of any type that conforms to the Equatable protocol without the overhead of type casting, resulting in more efficient code execution.

3. Type Safety:​

Generics contribute to improved type safety by catching potential errors at compile time. With generics, the Swift compiler ensures that you only operate on valid types and prevents type-related issues that might arise at runtime.

Conclusion​

Generics in Swift provide a powerful toolset for creating flexible and reusable code in iOS development. By leveraging generics, you can build more efficient and maintainable applications, enhance code reuse, and ensure type safety. Understanding and effectively utilizing generics will undoubtedly elevate your iOS development skills and improve the quality of your code.

Happy Coding!

MediaQuery as an InheritedModel in Flutter 3.10

Published: · Last updated: · 4 min read
Appxiom Team
Mobile App Performance Experts

In Flutter 3.10, an exciting change was introduced to the way MediaQuery is handled. MediaQuery, which provides access to the media information of the current context, was transformed into an InheritedModel. This change simplifies the process of accessing MediaQueryData throughout your Flutter application.

In this blog post, we will explore the implications of this change and how it affects the way we work with MediaQuery in Flutter.

Understanding InheritedModel​

Before diving into the specifics of how MediaQuery became an InheritedModel, let's briefly understand what InheritedModel is in Flutter. InheritedModel is a Flutter widget that allows the propagation of data down the widget tree. It provides a way to share data with descendant widgets without having to pass it explicitly through constructors.

In previous versions of Flutter, MediaQuery was not an InheritedModel, meaning that accessing MediaQueryData in nested widgets required some extra steps. However, starting from Flutter 3.10, MediaQuery became an InheritedModel, streamlining the process of accessing and using media-related information across your app.

Simplified Access to MediaQueryData​

With the migration of MediaQuery to an InheritedModel, accessing MediaQueryData became much simpler. Previously, you needed to use a StatefulWidget and a GlobalKey to store and retrieve MediaQueryData. However, after Flutter 3.10, you can directly use the MediaQuery.of(context) method to access the MediaQueryData for the current context.

The new approach allows you to obtain MediaQueryData anywhere in your widget tree without the need for additional boilerplate code. Simply provide the appropriate context, and you will have access to valuable information such as the size, orientation, and device pixel ratio.

Benefits of InheritedModel​

The shift of MediaQuery to an InheritedModel offers several benefits for Flutter developers:

  • Simplified Code: The direct usage of MediaQuery.of(context) eliminates the need for GlobalKey and StatefulWidget, resulting in cleaner and more concise code.

  • Improved Performance: As an InheritedModel, MediaQuery optimizes the propagation of changes to MediaQueryData throughout the widget tree. This means that only the necessary widgets will be rebuilt when media-related information changes, resulting in improved performance.

  • Enhanced Flexibility: By leveraging the InheritedModel approach, you can easily access MediaQueryData from any descendant widget within your app's widget tree. This flexibility enables you to respond dynamically to changes in the device's media attributes and adapt your UI accordingly.

Accessing MediaQueryData Before Flutter 3.10​

Before Flutter 3.10, accessing MediaQueryData required the use of a StatefulWidget and GlobalKey.

Let's take a look at the code example:

import 'package:flutter/material.dart';

class MyApp extends StatefulWidget {
@override
_MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
final GlobalKey<_MyAppState> _key = GlobalKey();
MediaQueryData _mediaQueryData;

@override
void initState() {
super.initState();
WidgetsBinding.instance.addPostFrameCallback((_) {
_mediaQueryData = MediaQuery.of(_key.currentContext);
});
}

@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
body: Center(
child: Text(
_mediaQueryData.size.toString(),
),
),
),
);
}
}

In the code snippet above, we define a StatefulWidget, MyApp, which holds a GlobalKey and the MediaQueryData object. Inside the initState method, we access the MediaQuery.of(_key.currentContext) to obtain the MediaQueryData. Finally, in the build method, we display the size of the device screen using the obtained MediaQueryData.

Accessing MediaQueryData in Flutter 3.10​

With the introduction of InheritedModel in Flutter 3.10, accessing MediaQueryData became much simpler.

Let's take a look at the updated code example:

import 'package:flutter/material.dart';

void main() {
runApp(
MaterialApp(
home: Scaffold(
body: Center(
child: Builder(
builder: (context) {
final mediaQueryData = MediaQuery.of(context);
return Text(
mediaQueryData.size.toString(),
);
},
),
),
),
),
);
}

In the updated code, we can now directly use MediaQuery.of(context) to access the MediaQueryData within any widget. We use the Builder widget to provide a new BuildContext where we can access the MediaQueryData. Inside the builder function, we obtain the mediaQueryData using MediaQuery.of(context) and display the size of the device screen using a Text widget.

Conclusion​

Flutter 3.10 introduced a significant change to the way we access MediaQueryData by transforming MediaQuery into an InheritedModel. This change simplifies the code and eliminates the need for StatefulWidget and GlobalKey to access MediaQueryData. By leveraging the power of InheritedModel, accessing MediaQueryData becomes a straightforward process using MediaQuery.of(context).

As a Flutter developer, staying up-to-date with the latest changes in the framework is crucial. Understanding the migration from StatefulWidget and GlobalKey to InheritedModel ensures that you can write more concise and efficient code. By embracing the simplified approach to accessing MediaQueryData, you can create responsive and adaptable user interfaces in your Flutter applications.

Building Memory Efficient iOS Apps Using Swift: Best Practices and Techniques

Published: · Last updated: · 4 min read
Appxiom Team
Mobile App Performance Experts

In the world of iOS app development, memory management plays a crucial role in delivering smooth user experiences and preventing crashes. Building memory-efficient apps is not only essential for maintaining good performance but also for optimizing battery life and ensuring the overall stability of your application.

In this blog post, we will explore some best practices and techniques for building memory-efficient iOS apps using Swift.

Automatic Reference Counting (ARC) in Swift​

Swift uses Automatic Reference Counting (ARC) as a memory management technique. ARC automatically tracks and manages the memory used by your app, deallocating objects that are no longer needed. It is essential to have a solid understanding of how ARC works to build memory-efficient iOS apps.

Avoid Strong Reference Cycles (Retain Cycles)​

A strong reference cycle, also known as a retain cycle, occurs when two objects hold strong references to each other, preventing them from being deallocated. This can lead to memory leaks and degrade app performance.

To avoid retain cycles, use weak or unowned references in situations where strong references are not necessary. Weak references automatically become nil when the referenced object is deallocated, while unowned references assume that the referenced object will always be available.

Example:

class Person {
var name: String
weak var spouse: Person?

init(name: String) {
self.name = name
}

deinit {
print("\(name) is being deallocated.")
}
}

func createCouple() {
let john = Person(name: "John")
let jane = Person(name: "Jane")

john.spouse = jane
jane.spouse = john
}

createCouple()
// Output: John is being deallocated.

In the example above, the spouse property is declared as a weak reference to avoid a retain cycle between two Person objects.

Use Lazy Initialization​

Lazy initialization allows you to delay the creation of an object until it is accessed for the first time. This can be useful when dealing with resource-intensive objects that are not immediately needed. By using lazy initialization, you can avoid unnecessary memory allocation until the object is actually required.

Example:

class ImageProcessor {
lazy var imageFilter: ImageFilter = {
return ImageFilter()
}()

// Rest of the class implementation
}

let processor = ImageProcessor()
// The ImageFilter object is not created until the first access to imageFilter property

Release Unused Resources​

Failing to release unused resources can quickly lead to memory consumption issues. It's important to free up any resources that are no longer needed, such as large data sets, images, or files. Use techniques like caching, lazy loading, and smart resource management to ensure that memory is efficiently utilized.

Optimize Image and Asset Usage​

Images and other assets can consume a significant amount of memory if not optimized properly. To reduce memory usage, consider the following techniques:

  • Use image formats that offer better compression, such as WebP or HEIF.

  • Resize images to the appropriate dimensions for their intended use.

  • Compress images without significant loss of quality.

  • Utilize image asset catalogs to generate optimized versions for different device resolutions.

  • Use image lazy loading techniques to load images on demand.

Implement View Recycling​

View recycling is an effective technique to optimize memory usage when dealing with large collections of reusable views, such as table views and collection views. Instead of creating a new view for each item, you can reuse existing views by dequeuing them from a pool. This approach reduces memory consumption and enhances the scrolling performance of your app.

Profile and Analyze Memory Usage​

Xcode provides powerful profiling tools to analyze the memory usage of your app. Use the Instruments tool to identify any memory leaks, heavy memory allocations, or unnecessary memory consumption. Regularly profiling your app during development allows you to catch and address memory-related issues early on. Also, you may use tools like Appxiom to detect memory leaks and abnormal memory usage.

Conclusion​

Building memory-efficient iOS apps is crucial for delivering a seamless user experience and optimizing the overall performance of your application. By understanding the principles of Automatic Reference Counting (ARC), avoiding strong reference cycles, lazy initialization, releasing unused resources, optimizing image and asset usage, implementing view recycling, and profiling memory usage, you can create iOS apps that are efficient, stable, and user-friendly.

Remember, memory optimization is an ongoing process, and it's essential to continuously monitor and improve memory usage as your app evolves. By following these best practices and techniques, you'll be well on your way to building memory-efficient iOS apps using Swift.

Using Method Channels to Enable Calls Between Native Code and Flutter Code

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

Flutter, a popular cross-platform development framework, allows developers to build high-performance applications with a single codebase. However, there are times when you need to integrate platform-specific functionality into your Flutter app. Method Channels provide a powerful mechanism to bridge the gap between Flutter and native code, enabling you to call native methods from Flutter and vice versa.

In this blog, we'll explore how to utilize Method Channels to invoke native code in both Android and iOS platforms from your Flutter app.

Prerequisites​

To follow along with this tutorial, you should have a basic understanding of Flutter and have Flutter SDK installed on your machine.

Additionally, make sure you have the necessary tools and configurations set up for Android and iOS development, such as Android Studio and Xcode.

Implementing Method Channels in Flutter​

Step 1: Create a Flutter Project Let's start by creating a new Flutter project. Open your terminal or command prompt and run the following command:

flutter create method_channel_demo
cd method_channel_demo

Step 2: Add Dependencies Open the pubspec.yaml file in your project's root directory and add the following dependencies:

dependencies:flutter:sdk: flutter
dev_dependencies:flutter_test:sdk: flutter

Save the file and run flutter pub get in your terminal to fetch the dependencies.

Step 3: Define the Native Method Channel Create a new Dart file named method_channel.dart in the lib directory. In this file, define a class called MethodChannelDemo that will encapsulate the native method channel communication. Add the following code:

import 'package:flutter/services.dart';

class MethodChannelDemo {
static const platform = MethodChannel('method_channel_demo');

static Future<String> getPlatformVersion() async {
return await platform.invokeMethod('getPlatformVersion');
}
}

In this code, we define a static platform object of type MethodChannel and associate it with the channel name 'method_channel_demo'. We also define a getPlatformVersion() method that invokes the native method 'getPlatformVersion' using the invokeMethod() function.

Step 4: Implement Native Code Next, let's implement the native code for both Android and iOS platforms.

For Android, open the MainActivity.kt file and import the necessary packages:

import android.os.Build.VERSION
import android.os.Build.VERSION_CODES
import io.flutter.embedding.android.FlutterActivity
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.plugins.GeneratedPluginRegistrant
import io.flutter.plugin.common.MethodChannel

Inside the MainActivity class, override the configureFlutterEngine() method and register the method channel:

class MainActivity : FlutterActivity() {
private val CHANNEL = "method_channel_demo"
override fun configureFlutterEngine(flutterEngine: FlutterEngine) {
super.configureFlutterEngine(flutterEngine)
GeneratedPluginRegistrant.registerWith(flutterEngine)

MethodChannel(flutterEngine.dartExecutor.binaryMessenger, CHANNEL)
.setMethodCallHandler { call, result ->
if (call.method == "getPlatformVersion") {
result.success("Android ${VERSION.RELEASE}")
} else {
result.notImplemented()
}
}
}
}

The code above sets up a method channel with the same name as defined in the Dart code. It handles the method call with a lambda function where we check the method name and return the Android platform version using the result.success() method.

For iOS, open the AppDelegate.swift file and import the necessary packages:

import UIKit
import Flutter
import UIKit.UIApplication
import UIKit.UIWindow

Inside the AppDelegate class, add the following code to register the method channel:

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
private let CHANNEL = "method_channel_demo"
override func application(
_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

GeneratedPluginRegistrant.register(with: self)
let controller = window?.rootViewController as! FlutterViewController
let channel = FlutterMethodChannel(name: CHANNEL,
binaryMessenger: controller.binaryMessenger)
channel.setMethodCallHandler({
(call: FlutterMethodCall, result: @escaping FlutterResult) -> Void in
if call.method == "getPlatformVersion" {
result("iOS " + UIDevice.current.systemVersion)
} else {
result(FlutterMethodNotImplemented)
}
})

return super.application(application, didFinishLaunchingWithOptions: launchOptions)
}
}

In this code, we create a method channel with the same name as defined in the Dart code. We handle the method call using a closure, check the method name, and return the iOS platform version using the result() method.

Step 5: Call Native Code from Flutter Now that we have set up the method channels and implemented the native code, let's invoke the native methods from Flutter.

Open the lib/main.dart file and replace its contents with the following code:

import 'package:flutter/material.dart';
import 'method_channel.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
appBar: AppBar(
title: const Text('Method Channel Demo'),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
FutureBuilder<String>(
future: MethodChannelDemo.getPlatformVersion(),
builder: (context, snapshot) {
if (snapshot.hasData) {
return Text('Platform version: ${snapshot.data}');
} else if (snapshot.hasError) {
return Text('Error: ${snapshot.error}');
}
return CircularProgressIndicator();
},
),
],
),
),
),
);
}
}

In this code, we import the method_channel.dart file and create a simple Flutter app with a centered column containing a FutureBuilder. The FutureBuilder calls the getPlatformVersion() method and displays the platform version once it's available.

Step 6: Run the App Finally, we're ready to run our app. Connect a physical device or start an emulator, then run the following command in your terminal:

flutter run

You have successfully implemented Method Channels to call native code in Android and iOS platforms from your Flutter app. You can now leverage this mechanism to access platform-specific APIs and extend the functionality of your Flutter applications.

Conclusion​

In this tutorial, we explored how to utilize Method Channels to invoke native code in Android and iOS platforms from a Flutter app. We covered the steps required to set up the method channels, implemented the native code for Android and iOS, and demonstrated how to call native methods from Flutter. By leveraging Method Channels, Flutter developers can access platform-specific features and create powerful cross-platform applications. Happy coding!

Exploring Apple WWDC 2023: Major Feature Announcements for iOS Developers

Published: · Last updated: · 8 min read
Don Peter
Cofounder and CTO, Appxiom

Apple's Worldwide Developers Conference (WWDC) is an eagerly anticipated annual event where the company unveils its latest software updates and development tools. In 2023, WWDC introduced several exciting features for developers, aimed at enhancing the app development experience and expanding the reach of apps across various Apple devices.

Let's dive into the major feature releases for developers announced at Apple WWDC 2023.

Swift Macro​

Version 5.9 introduced the concept of macros to Swift. Macros can be categorized into multiple smaller types.

  • ExpressionMacro to generate expression.

  • AccessorMacro to add getters and setters.

  • ConformanceMacro makes a type conform to a protocol.

Let's take a look at a basic macro to see how they function. Macros have the advantage of being executed during compile time.

Defining the AuthorMacro​

One useful macro can be created to generate the file author name.

In MyMacrosPlugin.swift:

import Foundation
import SwiftSyntax
import SwiftSyntaxMacros

public struct AuthorMacro: ExpressionMacro {
public static func expansion(
of node: some FreestandingMacroExpansionSyntax,
in context: some MacroExpansionContext
) -> ExprSyntax {
let argument = node.argumentList.first?.expression
let segments = argument.as(StringLiteralExprSyntax.self)?.segments

return "Autor: \(segments.first.content.text)"
}
}

This code defines a Swift macro named AuthorMacro that prints the author name from the string literal passed to it.

  • The AuthorMacro struct implements the ExpressionMacro protocol, allowing it to expand macros involving expressions.

  • The expansion function takes in a macro invocation and context and performs the following checks:

It ensures that the macro is invoked with a single argument that is a static string literal.

  • It appends the greeting message to the string.

The function returns an expression representing the constructed greeting message.

Declare Macro in Main Project

​

@freestanding(expression) 
public macro author(_ stringLiteral: String) -> String =
#externalMacro(module: "MyMacrosPlugin", type: "AuthorMacro")

Adding a string parameter and declaring the macro in our app target is a straightforward process. By incorporating the string parameter, we can enhance the macro's functionality and customize its behavior based on the specific needs of our application.

This flexibility allows us to pass dynamic string values to the macro, enabling more versatile and adaptable macro expansions.

Calling the Macro​

print(#author("Mark")) //prints "Author: Mark"

In order to use this macro simply call #author and pass the String as parameter. The macro will print the Author name.

Macros can be a powerful tool for improving the readability, performance, and functionality of your Swift code. However, it is important to use them carefully, as they can also make your code more difficult to understand and maintain.

Here are some tips for using macros:

  • Keep your macros short and simple.

  • Use descriptive names for your macros.

  • Document your macros thoroughly.

  • Test your macros thoroughly.

  • Use macros sparingly.

By following these tips, you can use macros to write more concise, efficient, and powerful Swift code.

SwiftData​

One of the highlights of Apple WWDC 2023 was the introduction of SwiftData. This new framework enables developers to seamlessly connect their data models to the user interface in SwiftUI.

​

Creating a Model

To enable saving instances of a model class using SwiftData, import the framework and annotate the class with the Model macro. This macro modifies the class to conform to the PersistentModel protocol, which SwiftData utilizes to analyze the class and generate an internal schema.

By default, SwiftData includes all noncomputed properties of a class, provided they use compatible types. The framework supports primitive types like Bool, Int, and String, as well as more complex value types such as structures, enumerations, and other types that conform to the Codable protocol.

import SwiftData

// Annotate with the @Model macro.
@Model
class Task {
var name: String
var role: String
var startDate: Date
var endDate: Date
var owner: Owner?
}

Leveraging Swift's macro system, developers can enjoy a streamlined API for modeling data using the familiar Codable protocol.

Persisting a Model​

To persist a model instance by SwiftData, insert the instance into the context using the insert function.

var task = Task(name: name, 
role: role,
startDate: startDate,
endDate: endDate)

context.insert(task)

After performing the insert, you have two options for saving the changes. The first option is to explicitly call the save() method on the context immediately. This will persist the changes to the underlying data store.

Alternatively, you can rely on the context's implicit save behavior. Contexts automatically track changes made to their known model instances, and these changes will be included in subsequent saves without requiring explicit invocation of the save() method. The context will take care of persisting the changes to the data store as needed.

Fetching a Model​

To fetch instances of a model and optionally apply search criteria and a preferred sort order in your SwiftUI view, you can use the @Query property wrapper. Additionally, by using the @Model macro, you can add Observable conformance to your model classes.

This enables SwiftUI to automatically refresh the containing view whenever changes occur to any of the fetched instances.

import SwiftUI
import SwiftData

struct ContentView: View {
@Query(sort: \.endDate, order: .reverse) var allTasks: [Task]

var body: some View {
List {
ForEach(allTasks) { task in
TaskView(for: task)
}
}
}
}

WidgetKit​

This major feature release empowers developers to extend their app's content beyond the app itself. With WidgetKit, developers can create glanceable, up-to-date experiences in the form of widgets, Live Activities, and watch complications.

@main
struct WeatherStatusWidget: Widget {
var body: some WidgetConfiguration {
StaticConfiguration(
kind: "",
provider: WeatherStatusProvider()
) { entry in
WeatherStatusView(entry.weatherStatus)
}
.configurationDisplayName("Weather Status")
.description("Shows an overview of your weather status")
.supportedFamilies([.systemSmall])
}
}

The technology and design similarities among widgets, Live Activities, and watch complications facilitate seamless feature development and usage across different contexts.

ActivityKit​

ActivityKit offers developers the ability to create Live Activities that provide live updates and interactions directly from their apps. Live Activities can appear in prominent positions such as the Lock Screen, Dynamic Island, and as banners on the Home Screen. Users can view real-time information, launch the app, and perform specific functionalities through buttons and toggles, without fully opening the app.

import SwiftUI
import WidgetKit

@main
struct FoodOrderActivityWidget: Widget {
var body: some WidgetConfiguration {
ActivityConfiguration(for: FoodOrderAttributes.self) { context in

} dynamicIsland: { context in

}
}
}

By leveraging SwiftUI and WidgetKit, developers can share code between widgets and Live Activities, making it easier to build engaging experiences.

Observable​

The Observable protocol simplifies the implementation of data change notifications. By attaching the Observable macro to custom types, developers indicate conformance to the Observable protocol. This protocol enables types to emit notifications to observers whenever the underlying data changes.

@Observable final class Animal {
var name: String = ""
var sleeping: Bool = false

init(name: String, sleeping: Bool = false) {
self.name = name
self.sleeping = sleeping
}
}

To enable change tracking, use the withObservationTracking(_:onChange:) function. In the provided code example, this function is used to call the onChange closure when the name property of a car changes. However, it does not trigger the closure when the sleeping flag of the car changes. This behavior occurs because the function only tracks properties that are read within its apply closure, and in this case, the sleeping property is not read within that closure.

func render() {
withObservationTracking {
for animal in animals { //apply closure
print(animal.name)
}
} onChange: { //onChange closure
print("Call UI updation.")
}
}

The Observable protocol provides a convenient way to handle data updates and build reactive interfaces, enhancing the overall user experience of the app.

WorkoutKit​

This powerful framework offers models and utilities for creating and previewing workout compositions in iOS and watchOS apps. Developers can design various types of workouts, including CustomWorkoutComposition, GoalWorkoutComposition, and others catering to different fitness activities. The framework provides methods for validating, exporting, and previewing workouts, allowing users to save compositions to the Workout app. Furthermore,

WorkoutKit enables developers to create and manage workout schedules, sync scheduled compositions to Apple Watch, and query completed workouts.

PayLaterView​

Showcasing Apple Pay Later Feature Apple Pay Later, a new financial service, received special attention at WWDC 2023. To enhance its visibility, Apple introduced the PayLaterView, a dedicated view for displaying the Apple Pay Later visual merchandising widget.

VisionOS​

One of the key features of VisionOS is the ability to create multiple windows within the app. These windows, built using SwiftUI, provide familiar views and controls while enabling developers to add depth by incorporating stunning 3D content. With VisionOS, it is possible to further enhance the app's depth by incorporating 3D volumes.

These volumes, powered by RealityKit or Unity, allows to showcase captivating 3D content that can be viewed from any angle within the Shared Space or an app's Full Space. The flexibility of volumes helps to craft engaging experiences that captivate and delight app users.

By default, apps in VisionOS launch into the Shared Space, where they coexist side-by-side, akin to multiple apps on a Mac desktop. Utilizing windows and volumes, apps can display their content within this shared environment, giving users the ability to freely reposition and interact with these elements. For a truly immersive experience, apps can open a dedicated Full Space, where only their content is visible. Within a Full Space, apps can leverage windows and volumes, create unbounded 3D content, open portals to different worlds, or provide users with a fully immersive environment.

Conclusion​

Apple WWDC 2023 brought significant enhancements for developers, offering tools and frameworks to streamline data modeling, extend app content through widgets and Live Activities, simplify data change notifications, optimize workout compositions, and showcase new financial features.

These advancements empower developers to create more immersive and feature-rich applications across Apple's ecosystem of devices.

Data Persistence in Flutter

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

In today's app development landscape, databases play a crucial role in managing and storing data. Flutter, a popular cross-platform framework, offers various options for integrating databases into your applications.

In this blog, we will explore the fundamental database concepts in Flutter and provide code examples to illustrate their implementation. So, let's dive in and learn how to effectively work with databases in Flutter!

Introduction to Databases​

A database is a structured collection of data that allows efficient storage, retrieval, and manipulation of information. In the context of app development, databases are used to store and manage data persistently, enabling apps to function seamlessly even when offline or across different devices.

Local Data Persistence in Flutter​

Local data persistence refers to the storage of data on the device itself. Flutter provides several libraries and techniques for local data persistence.

Some popular options include:

Shared Preferences​

Shared Preferences is a simple key-value store that allows you to store primitive data types such as strings, integers, booleans, etc. It's suitable for storing small amounts of data that don't require complex querying.

import 'package:shared_preferences/shared_preferences.dart';

void saveData() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
await prefs.setString('username', 'JohnDoe');
}

void loadData() async {
SharedPreferences prefs = await SharedPreferences.getInstance();
String username = prefs.getString('username');
print('Username: $username');
}

Hive​

Hive is a lightweight and fast NoSQL database for Flutter. It offers a simple key-value store as well as support for more complex data structures. Hive is known for its excellent performance and ease of use.

import 'package:hive/hive.dart';

void saveData() async {
var box = await Hive.openBox('myBox');
await box.put('username', 'JohnDoe');
}

void loadData() async {
var box = await Hive.openBox('myBox');
String username = box.get('username');
print('Username: $username');
}

SQLite Database Integration​

SQLite is a widely used relational database management system (RDBMS) that provides a self-contained, serverless, and zero-configuration SQL database engine. Flutter offers seamless integration with SQLite, enabling you to create and manage structured databases efficiently.

Setting up SQLite in Flutter​

To use SQLite in Flutter, you need to include the sqflite package in your pubspec.yaml file and import the necessary dependencies.

import 'package:sqflite/sqflite.dart';
import 'package:path/path.dart';

Future<Database> initializeDatabase() async {
String path = join(await getDatabasesPath(), 'my_database.db');
return await openDatabase(
path,
version: 1,
onCreate: (Database db, int version) async {
// Create tables and define schemas
await db.execute(
'CREATE TABLE users (id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT)',
);
},
);
}

Performing CRUD Operations with SQLite​

Once the database is initialized, you can perform various CRUD (Create, Read, Update, Delete) operations on it using SQL queries.

Future<void> insertUser(User user) async {
final db = await database;
await db.insert(
'users',
user.toMap(),
conflictAlgorithm: ConflictAlgorithm.replace,
);
}

Future<List<User>> getUsers() async {
final db = await database;
final List<Map<String, dynamic>> maps = await db.query('users');
return List.generate(maps.length, (i) {
return User(
id: maps[i]['id'],
name: maps[i]['name'],
);
});
}

Working with Firebase Realtime Database​

Firebase Realtime Database is a NoSQL cloud-hosted database that enables real-time data synchronization across devices. It offers seamless integration with Flutter, allowing you to store and sync structured data easily.

Setting up Firebase Realtime Database​

To use Firebase Realtime Database in Flutter, you need to create a Firebase project, add the necessary dependencies in your pubspec.yaml file, and configure Firebase in your Flutter app.

Performing CRUD Operations with Firebase Realtime Database​

Firebase Realtime Database uses a JSON-like structure to store and organize data. You can perform CRUD operations using the Firebase SDK.

import 'package:firebase_database/firebase_database.dart';

void insertUser(User user) {
DatabaseReference usersRef =
FirebaseDatabase.instance.reference().child('users');
usersRef.push().set(user.toJson());
}

void getUsers() {
DatabaseReference usersRef =
FirebaseDatabase.instance.reference().child('users');
usersRef.once().then((DataSnapshot snapshot) {
Map<dynamic, dynamic> values = snapshot.value;
values.forEach((key, values) {
print('ID: $key');
print('Name: ${values['name']}');
});
});
}

Implementing GraphQL with Hasura and Flutter​

GraphQL is a query language for APIs that provides a flexible and efficient approach to data fetching. Hasura is an open-source engine that provides instant GraphQL APIs over databases. By combining Flutter, Hasura, and GraphQL, you can create powerful and responsive apps with real-time data capabilities.

Setting up Hasura and GraphQL in Flutter​

To integrate Hasura and GraphQL into your Flutter app, you need to set up a Hasura server and define your database schema. Then, use the graphql package in Flutter to interact with the GraphQL API.

Performing GraphQL Operations with Hasura and Flutter​

With GraphQL, you can define queries and mutations to fetch and modify data from the server.

import 'package:graphql_flutter/graphql_flutter.dart';

void getUsers() async {
final String getUsersQuery = '''
query {
users {
id
name
}
}
''';

final GraphQLClient client = GraphQLClient(
cache: GraphQLCache(),
link: HttpLink('https://your-hasura-endpoint.com/v1/graphql'),
);

final QueryResult result = await client.query(QueryOptions(
document: gql(getUsersQuery),
));

if (result.hasException) {
print(result.exception.toString());
} else {
final List<dynamic> users = result.data['users'];
for (var user in users) {
print('ID: ${user['id']}');
print('Name: ${user['name']}');
}
}
}

Conclusion​

In this blog, we explored various database concepts in Flutter and learned how to implement them using different database technologies. We covered local data persistence, SQLite integration, Firebase Realtime Database, and GraphQL with Hasura.

With these skills, you can efficiently manage and store data in your Flutter applications. Experiment with these concepts and choose the most suitable database solution based on your app's requirements.

Happy coding!

Remember to import the necessary packages and dependencies to execute the code examples provided in this blog.

Quick-Start Guide for Using Core Data with SwiftUI

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

In the world of iOS app development, Core Data is a powerful framework that enables developers to work with a persistent storage solution. With the advent of SwiftUI, Apple's modern declarative framework for building user interfaces, integrating Core Data seamlessly into SwiftUI apps has become even easier and more efficient.

In this blog post, we will explore how to use Core Data with SwiftUI, discussing the fundamental concepts and providing a step-by-step guide along with code examples.

Prerequisites​

To follow along with this tutorial, you should have basic knowledge of SwiftUI and a working understanding of the Swift programming language. Additionally, make sure you have Xcode installed on your Mac.

Setting Up the SwiftUI Project​

  1. Launch Xcode and create a new SwiftUI project by selecting "File" -> "New" -> "Project" and choosing the "App" template with SwiftUI selected.

  2. Provide a name for your project, select the appropriate options, and click "Next" to create the project.

  3. Once the project is created, open the ContentView.swift file and replace its contents with the following code:

import SwiftUI

struct ContentView: View {
var body: some View {
Text("Hello, Core Data!")
}
}

struct ContentView_Previews: PreviewProvider {
static var previews: some View {
ContentView()
}
}

Understanding Core Data​

Core Data is an object graph and persistence framework provided by Apple. It allows you to manage the model layer objects in your app, including their persistence and retrieval. Core Data uses SQLite as the default persistent store, but it also supports other options.

Core Data Entities​

An entity in Core Data represents a table in the underlying data model. Each entity contains attributes and relationships, which define its structure. To create an entity, follow these steps:

  1. Open the project navigator in Xcode and select the project file.

  2. Go to the "Data Model" file, typically named YourProjectName.xcdatamodeld.

  3. Click on the "+" button to add a new entity and provide a name for it (e.g., "Task").

  4. Add attributes and relationships to the entity by clicking on the "+" button in the "Attributes" and "Relationships" sections.

Creating a Core Data Model​

  1. In the project navigator, select the project file.

  2. Go to the "Data Model" file.

  3. Click on the "+" button to add a new model version.

  4. Select the newly created model version, and in the "Editor" menu, choose "Add Model Configuration" to create a configuration for your model.

Working with Core Data in SwiftUI​

  1. Create a new SwiftUI view for displaying your Core Data entities. For example, create a new SwiftUI file called TaskListView.swift with the following code:
import SwiftUI

struct TaskListView: View {
@Environment(\.managedObjectContext) private var viewContext

@FetchRequest(
sortDescriptors: [NSSortDescriptor(keyPath: \Task.createdAt, ascending: true)],
animation: .default)
private var tasks: FetchedResults<Task>

var body: some View {
NavigationView {
List {
ForEach(tasks) { task in
Text(task.title ?? "Untitled")
}
.onDelete(perform: deleteTasks)
}
.navigationBarItems(trailing: EditButton())
.navigationTitle("Tasks")
}
}

private func deleteTasks(offsets: IndexSet) {
withAnimation {
offsets.map { tasks[$0] }.forEach(viewContext.delete)

do {
try viewContext.save()
} catch {
let nsError = error as NSErrorfatalError("Unresolved error \(nsError), \(nsError.userInfo)")
}
}
}
}

struct TaskListView_Previews: PreviewProvider {
static var previews: some View {
TaskListView().environment(\.managedObjectContext, PersistenceController.preview.container.viewContext)
}
}
  1. In the TaskListView, we use the @FetchRequest property wrapper to fetch the Task entities from the Core Data managed object context. We specify a sort descriptor to order the tasks by their creation date.

  2. The TaskListView contains a list of tasks fetched from Core Data. We also implement the ability to delete tasks using the onDelete modifier.

  3. To enable Core Data integration, we access the managed object context through the @Environment(.managedObjectContext) property wrapper.

  4. Finally, we add the TaskListView as the root view in the ContentView.

Persisting Data with Core Data​

  1. Open the YourProjectName.xcdatamodeld file and create a new entity called "Task".

  2. Add attributes to the "Task" entity, such as "title" (String) and "createdAt" (Date).

  3. Create a new Swift file named Task+CoreDataProperties.swift and add the following code:

import Foundation
import CoreData

extension Task {
@nonobjc public class func fetchRequest() -> NSFetchRequest<Task> {
return NSFetchRequest<Task>(entityName: "Task")
}

@NSManaged public var title: String?
@NSManaged public var createdAt: Date?
}

extension Task: Identifiable {}
  1. Build and run your app, and you should see the list of tasks fetched from Core Data. You can add, delete, and modify tasks, and the changes will be persisted automatically.

Conclusion​

In this blog post, we explored how to use Core Data with SwiftUI, integrating a persistent storage solution seamlessly into our app. We learned the basics of Core Data, created entities and attributes, and built a SwiftUI view that displays and manages data from Core Data. By leveraging the power of Core Data and SwiftUI together, you can create robust and efficient iOS apps with ease.

Remember, Core Data offers many advanced features and customization options that we haven't covered in this tutorial. I encourage you to dive deeper into the Core Data framework to unleash its full potential in your SwiftUI projects.

Happy coding!

Building Memory Efficient Flutter Apps

Published: · Last updated: · 3 min read
Appxiom Team
Mobile App Performance Experts

In today's mobile app development landscape, memory efficiency plays a crucial role in delivering a smooth and responsive user experience. Flutter, Google's open-source UI toolkit, allows developers to create cross-platform apps with a rich set of features. However, as apps grow in complexity and data handling requirements, it becomes essential to optimize memory usage.

In this blog, we will explore some strategies and techniques to write memory efficient code in Flutter apps, ensuring optimal performance and user satisfaction.

1. Use Stateless Widgets​

In Flutter, widgets are the building blocks of the UI. To conserve memory, prefer using StatelessWidget over StatefulWidget wherever possible. Stateless widgets are immutable and do not maintain any internal state. They consume less memory and are ideal for UI components that do not require frequent updates or interaction.

Example:

class MyWidget extends StatelessWidget {
final String data;

const MyWidget(this.data);

@override
Widget build(BuildContext context) {
return Text(data);
}
}

2. Dispose of Resources​

When using resources like databases, network connections, or streams, it's crucial to release them properly to avoid memory leaks. Use the dispose() method provided by various Flutter classes to release resources when they are no longer needed. For example, in a StatefulWidget, override the dispose() method to clean up resources.

Example:

class MyStatefulPage extends StatefulWidget {
@override
_MyStatefulPageState createState() => _MyStatefulPageState();
}

class _MyStatefulPageState extends State<MyStatefulPage> {
DatabaseConnection _connection;

@override
void initState() {
super.initState();
_connection = DatabaseConnection();
}

@override
void dispose() {
_connection.close();
super.dispose();
}

// Rest of the widget code...
}

3. Use Efficient Data Structures​

Choosing the right data structures can significantly impact memory consumption. Flutter provides various collections such as List, Set, and Map. However, be mindful of the memory requirements when dealing with large datasets. Consider using specialized collections like SplayTreeSet or LinkedHashMap that provide efficient look-up or iteration operations.

Example:

import 'dart:collection';

void main() {
var orderedSet = SplayTreeSet<String>();
orderedSet.addAll(['Apple', 'Banana', 'Orange']);

var linkedMap = LinkedHashMap<String, int>();
linkedMap['Alice'] = 25;
linkedMap['Bob'] = 30;
linkedMap['Charlie'] = 35;
}

4. Optimize Image Usage​

Images often consume a significant portion of memory in mobile apps. To reduce memory usage, consider optimizing and compressing images before using them in your Flutter app. Tools like flutter_image_compress can help reduce the image size without compromising quality. Additionally, leverage techniques like lazy loading and caching to load images only when necessary.

Example:

import 'package:flutter_image_compress/flutter_image_compress.dart';

Future<void> compressImage() async {
var compressedImage = await FlutterImageCompress.compressWithFile(
'original.jpg',
quality: 85,
);

// Store or display the compressed image.
}

5. Use ListView.builder for Large Lists​

When displaying large lists, prefer using ListView.builder instead of ListView to optimize memory usage. ListView.builder lazily creates and recycles widgets as they come into and go out of view. This approach avoids creating all the widgets upfront, conserving memory and improving performance.

Example:

ListView.builder(
itemCount: 1000,
itemBuilder: (context, index) {
return ListTile(
title: Text('Item $index'),
);
},
);

Conclusion​

Writing memory efficient code is crucial for creating high-performance Flutter apps. By using stateless widgets, disposing of resources properly, leveraging efficient data structures, optimizing image usage, and utilizing ListView.builder, you can significantly reduce memory consumption and enhance the overall user experience. By adopting these practices, you'll be well on your way to building robust and efficient Flutter applications.

Remember, optimizing memory usage is an ongoing process, and profiling your app's memory consumption using tools like the Flutter DevTools can provide valuable insights for further improvements.

Happy coding!

Using ARKit with Swift to Build AR Applications in iOS

Published: · Last updated: · 5 min read
Appxiom Team
Mobile App Performance Experts

Augmented Reality (AR) has become an exciting technology that allows developers to create immersive experiences by overlaying virtual objects onto the real world. ARKit, Apple's framework for building AR applications, provides powerful tools and features to integrate AR into iOS apps using the Swift programming language.

In this blog post, we will explore how to use ARKit with Swift to create an AR application step by step.

Prerequisites​

Before we dive into coding, make sure you have the following prerequisites:

  • A Mac running macOS 10.13.2 or later.

  • Xcode 9.0 or later.

  • An iOS device with an A9 or later processor, running iOS 11.0 or later.

  • Basic knowledge of Swift programming language and iOS app development.

Setting Up ARKit​

To get started, let's create a new iOS project in Xcode and configure it for ARKit. Follow these steps:

  • Open Xcode and click on "Create a new Xcode project."

  • Choose "Augmented Reality App" template under the "App" category.

  • Enter the product name, organization identifier, and select Swift as the language.

  • Choose a location to save your project and click "Create."

Exploring the Project Structure​

Once the project is created, let's take a quick look at the project structure:

  • AppDelegate.swift: The entry point of the application.

  • ViewController.swift: The default view controller for the ARKit app.

  • Main.storyboard: The user interface layout for the app.

  • Assets.xcassets: The asset catalog where you can add images and other resources.

  • Info.plist: The property list file that contains the configuration settings for the app.

Understanding the View Controller​

The ViewController.swift file is the main view controller for our ARKit app. Open the file and let's explore its structure:

import UIKit
import ARKit

class ViewController: UIViewController {

@IBOutlet var sceneView: ARSCNView!

override func viewDidLoad() {
super.viewDidLoad()

// Set the view's delegate
sceneView.delegate = self
// Create a new scene
let scene = SCNScene()

// Set the scene to the view
sceneView.scene = scene
}

override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)

// Create a session configuration
let configuration = ARWorldTrackingConfiguration()

// Run the view's session
sceneView.session.run(configuration)
}

override func viewWillDisappear(_ animated: Bool) {
super.viewWillDisappear(animated)

// Pause the view's session
sceneView.session.pause()
}
}

extension ViewController: ARSCNViewDelegate {

}

The ViewController class inherits from UIViewController and conforms to the ARSCNViewDelegate protocol. It contains an ARSCNView object named sceneView, which is responsible for rendering the AR scene.

In the viewDidLoad() method, we set the sceneView delegate to self and create a new SCNScene object. We then assign the created scene to the sceneView.scene property.

In the viewWillAppear() method, we create an ARWorldTrackingConfiguration object, which is the primary configuration for AR experiences. We run the AR session by calling sceneView.session.run() with the created configuration.

Finally, in the viewWillDisappear() method, we pause the AR session by calling sceneView.session.pause().

Adding 3D Objects to the Scene​

To add 3D objects to the AR scene, we need to implement the ARSCNViewDelegate methods. Modify the extension block in ViewController.swift as follows:

extension ViewController: ARSCNViewDelegate {

func renderer(_ renderer: SCNSceneRenderer, didAdd node: SCNNode, for anchor: ARAnchor) {
// Check if the added anchor is an ARPlaneAnchor
guard let planeAnchor = anchor as? ARPlaneAnchor else { return }

// Create a new plane node with the anchor's dimensions
let planeNode = createPlaneNode(with: planeAnchor)

// Add the plane node to the scene
node.addChildNode(planeNode)
}

private func createPlaneNode(with anchor: ARPlaneAnchor) -> SCNNode {
// Create a plane geometry with the anchor's dimensions
let planeGeometry = SCNPlane(width: CGFloat(anchor.extent.x), height: CGFloat(anchor.extent.z))

// Set the plane's color
planeGeometry.materials.first?.diffuse.contents = UIColor.blue.withAlphaComponent(0.5)

// Create a plane node with the geometry
let planeNode = SCNNode(geometry: planeGeometry)

// Position the plane node at the anchor's center
planeNode.position = SCNVector3(anchor.center.x, 0, anchor.center.z)

// Rotate the plane node to match the anchor's orientation
planeNode.eulerAngles.x = -.pi / 2
return planeNode
}
}

In the renderer(_:didAdd:for:) method, we check if the added anchor is an ARPlaneAnchor. If it is, we call the createPlaneNode(with:) method to create a plane node and add it to the scene.

The createPlaneNode(with:) method takes an ARPlaneAnchor as input and creates an SCNPlane geometry with the anchor's dimensions. We set the plane's color to blue with 50% transparency. Then, we create an SCNNode with the plane geometry, position it at the anchor's center, and rotate it to match the anchor's orientation. Finally, we return the plane node.

Running the AR App​

Now that we have implemented the basic setup and added functionality to display plane nodes, let's run the AR app on a compatible iOS device. Follow these steps:

  • Connect your iOS device to your Mac.

  • Select your iOS device as the build destination in Xcode.

  • Click the "Play" button or press Command+R to build and run the app on your device.

Once the app is launched, point the camera at a flat surface, such as a tabletop or floor. As the ARKit detects and recognizes the surface, it will display a blue semi-transparent plane overlay on it.

Conclusion​

In this blog post, we learned how to use ARKit with Swift to create an AR application in iOS. We explored the project structure, understood the view controller, and added 3D plane nodes to the scene using the ARSCNViewDelegate methods.

This is just the beginning of what you can achieve with ARKit. You can further enhance your AR app by adding custom 3D models, interactive gestures, and more.

Have fun exploring the possibilities of AR with Swift and ARKit!

Happy coding!