As a primary backend developer, one of the most ambiguous parts of my job involves frontend code reviews. Give me a Ruby on Rails PR and I can nitpick it all day long but send me a React PR and I feel like I’m being asked to review an academic paper on the latest developments in String Theory.  Part of the issue is that frontend code necessarily contains a significant amount of boilerplate code (CSS and HTML come to mind.) It can be difficult to tell what’s good and what could use improvement when your eyes are lost in a sea of green text:

So, I asked some of our frontend developers at Unosquare if they had any tips for creating or reviewing frontend PRs. I’d love to share some of their suggestions!

Tip #1: Add Screenshots!

Kudos to Vincent Lopez, one of our backend developers, for contributing this tip! Far and away the most useful tip our team has found with front-end code reviews is that they need screenshots, videos, or a demo app showcasing the UX/UI look and feel. Is there enough contrast? Do the designs look consistent with other areas of the app? Are the animations smooth? Is the flow between screens logical? These aspects of front-end features are nearly impossible to decipher by simply staring at code, but add a visual layer atop the review, and all of a sudden you gain a more complete picture.

Here’s a couple of real-world examples of how Rich Dubay (one of our Unosquare front-end developers on the Solid Lives team) structures his frontend PRs:

The compression is difficult to see in the screenshot, but you get the idea from the combination of the title, description, and screenshots exactly what the problem was and how it looks after it’s been fixed.

Here’s another one of Rich’s examples:

The before and after images clearly show how the wrapping bug was fixed. This is not only helpful for other developers, but it also gives the QA tester confidence in what they should expect the screen to look like after the fix is deployed to the testing environment.

Tip #2: Add Descriptive Comments

You may have heard developers say “Let the code speak for itself. Avoid comments!” I agree that you should attempt to make your code as self-descriptive as possible; however, there is a critically missing piece of information in that advice: source control comments are extremely valuable. They provide critical information relevant to the entire context of the change and are a developer’s opportunity to explain themselves to other developers in the most natural way possible. I’ll let Josh Babcock, another one of our front-end Unosquare developers on the Solid Lives team, demonstrate this with one of his recent PRs:

In my opinion, this is a remarkably descriptive PR. It’s got it all:

• The ticket number related to the change: “Jb/sljd 1105 edit”
• A description of the scope of this change: “This is for Graduation tickets 1-5 (if curious all are in code review”)
• A list of API changes
• A list of major changes, particularly noting new UI elements
• Todo items: “***** I left out some Spanish strings. I’m waiting for Stepf to finish the media library tickets first.”
• Screenshots (as we expressed in Tip #1)

The changes above are considerations you should be thinking about when creating a PR for a front-end code review (frankly, even for a back-end review.)

Tip #3: Be Proactive with Questions

One of the most useful features of Github is the ability of the PR author to post comments on specific lines of code. This is remarkably useful for asking questions such as, “Is this the best way to do this?” or “I had to do it this way because…” This clues other developers in that they should pay special attention to the lines of code mentioned and offer follow-up if needed. Here’s Josh and Rich with a good example of that:

Josh is humble enough to ask about whether his solution is the best way to do something, and Rich responds with not only a clear and concise opinion, but also an example of how he could refactor it. These types of discussions are wonderful async ways to pair program. We do our best work as developers when we have team members supporting us!

Tip #4: Consider The Various Visual States (Matt Koehler)

While the above tips were a bit more meta, this one from one of our front-end developers, Matt Koehler, is more concrete. He suggests thinking about what a screen should look like when it’s in various states. For example, what should a screen look like when it’s loading? If you’re reviewing the PR, you can easily look for elements like spinners or loading text in the code to double check their presence as well as examining screenshots of the app in action.

Form state is another aspect to consider. If data is invalid, avoid confusing your user with disabled submit buttons. Instead, keep the buttons active but display a helpful error message on press explaining why the form can’t be submitted. Like loading states, this can be inspected in a PR by examining the form code’s onSubmit logic. Are there good validation messages in place? What does the form submission look like in an invalid state? When authoring a PR, adding screenshots showcasing the invalid form state alongside the valid state are very useful for this reason.

Conclusion

I’m sure there are dozens of other tips for front-end code reviews. These are but a few, but I hope you will find them helpful in your future reviews. Most of all, I hope they will get you thinking about the various ways you can both author and review front-end code.

We developers are often so excited that we’ve completed coding a feature that we forget that simply pushing code is by no means the last step in its journey. Avoid hitting the “Create Pull Request” button and blindly leaving the defaults in place. Think about what it is you want to communicate with your team that will help make the code the best it can possibly be.

Similarly, when reviewing large chunks of code, avoid cursory scans and instead visualize what it’s like when it’s actually running in the user interface. Examine it like a sculpture from different angles. Inspect it in various lights. There’s much more to front-end code than meets the eye, but if we consider it critically, we can improve the UI and UX, avoid bugs, craft clean code, and better communicate with fellow team members. Happy reviewing!

What Exactly Are PWAs?

Imagine a web app that feels like it was born to be on your phone. That’s a PWA. These web apps have been jazzed up with some seriously cool features, like offline capabilities, push notifications, and home screen icons. The big win here? They can run on any device with a web browser, making them incredibly accessible.

And What About Native Apps?

Native apps are the homebodies of the app world; they like to stick to their kind. Designed specifically for individual platforms like iOS or Android, they’re built in the platform’s native programming language. This manner of build allows them to exploit the device’s hardware and capabilities fully, making them robust and feature-packed.

A Brief Stroll Down Memory Lane: The Origins of PWAs and Native Apps

Native Apps: The OGs of Mobile Experience

Let’s go back to 2007. The world got its first taste of the iPhone, and boom! Native apps took center stage. These apps were the brainchild of platform-centric development. Apple’s iOS and later Google’s Android each had their app ecosystems, complete with their programming languages—Objective-C/Swift for iOS and Java/Kotlin for Android. The concept was simple: create apps that leverage the full firepower of the device they’re on.

Native apps exploded in popularity because of their custom-tailoring for the device’s hardware and software, allowing them to tap directly into a phone’s camera, GPS, and even accelerometer. Fast forward to today, and native apps are still the go-to for businesses that need high-performance, feature-rich applications. They’re like the Swiss Army knives of the app world—packed with features and versatile but somewhat bulky.

Progressive Web Apps: The New Kids with Big Dreams

Now, fast-forward to around 2015. The web was evolving, smartphones were in almost every pocket, and a gap existed. Web apps existed but lacked the charm and capabilities of native apps. Enter Progressive Web Apps (PWAs), a term coined by Google engineers Alex Russell and Frances Berriman.

PWAs aimed to combine the best of web and mobile and promised the universality of the web—accessible to anyone, anywhere, on any device—with features that used to be exclusive to native apps. Think offline access, push notifications, and home screen icons.

PWAs were able to offer a close-to-native experience without the need for app stores or device-specific programming. They’re like the food trucks of the tech world—easier to set up more accessible, but with a slightly limited menu compared to a full-blown restaurant (read: native app).

The Nitty-Gritty: How Do PWAs and Native Apps Differ?

Here’s the lowdown:

• Accessibility: PWAs are the social butterflies that get along with any device sporting a web browser. Native apps, however, play favorites with specific platforms.
• Performance: Sure, native apps can be Hercules-strong and loaded with features, but they might keep you waiting at the door with slower load times.
• Development: Building a PWA is generally a walk in the park compared to the marathon that is native app development.
• Distribution: While PWAs can roll out via the web with the snap of a finger, native apps need to go through the formalities of app stores.

The Good, The Bad, and The PWA

Pros:

• Accessible: Open to anyone with a web browser.
• Fast: These babies load in a flash, even on less-than-stellar connections.
• Engaging: Think offline support and push notifications to keep your users hooked.
• Secure: Locked and loaded with HTTPS, just like their native counterparts.

Cons:

• Less Powerful: Expect them to utilize only some nook and cranny of device features.
• Adoption: They’re still the new kid on the block, so their user base might be less significant.

Native Apps: What’s to Love and What’s Less Lovely

Pros:

• Powerhouse: These apps can flex all the device’s muscles—camera, mic, you name it.
• Feature-Rich: Think of a feature, and a native app can probably support it.
• Widespread Adoption: They’re the popular kids in the app world, so reaching users is more straightforward.

Cons:

• Limited Access: They’re picky about the devices they’ll hang out with.
• Slow to Load: Patience is essential; they can take their sweet time loading.
• Complex Development: More features often mean more development headaches.

Factors to Weigh in Your Decision

1. Target Audience: Who are you looking to impress? A PWA might be the way to go if your crowd uses various devices.
2. Features: Need the whole shebang when it comes to device features? Then go native.
3. Resources: Limited time or budget? A PWA can be your fast track to app glory.
4. Distribution: Think about how you’ll get your app into people’s hands. The web makes PWAs easy to share, whereas native apps need to pass the app store test.

Final Thoughts

Native Apps were born in an era when the concept of a “smartphone” was still new and mind-blowing and engineered to squeeze every ounce of capability out of those early devices. PWAs, on the other hand, were conceived as a solution to the limitations of web apps, offering a universal alternative to the platform-specific world of Native Apps.

The PWA vs. Native App debate doesn’t have a one-size-fits-all answer. Your best move depends on what you need and what you’ve got to work with. Armed with this knowledge, you’re well on your way to choosing to fit your business like a glove.

World-Class End to End Digital Product Design

Each on our own, Catalyst and Unosquare offer clients exceptional services in UX design and digital engineering, respectively.  Combined, however, we can offer clients end-to-end digital strategy, design and delivery – and from anywhere in the world.  Our joining forces with Unosquare, a giant in the world of Digital Product Nearshoring, means our clients can save time and money and know that their project is being managed well as we have one dedicated team to manage the project from idea to implementation.  Imagine a world where software isn’t just efficient and functional, visually stunning, user-friendly, and designed with the end user in mind. That’s the world we’re aiming to create.

Elevating User Experience to the Next Level

One of the key aspects that sets Catalyst UX apart is our domain expertise and ability to understand the intricate needs of our clients in specific, highly regulated industries. By combining this with Unosquare’s prowess in software development, we’re now in an even better position to deliver exceptional user experience in the most challenging settings.

Seamless Integration, Enhanced Delivery

While our clients have always appreciated our UI/UX design services, with the added strength of Unosquare, we can ensure even smoother integration with digital design. This combination of skills means faster turnarounds, more cohesive products, and, we hope, happier clients.

Looking Forward With Excitement

Being part of the Unosquare family aligns with our vision of delivering top-notch digital solutions. It offers an opportunity to be part of a legacy—the impressive 8-year streak on the Inc. 5000 list. To our clients, partners, and the incredible team at Unosquare: Let’s make waves in the digital product design universe. The sky’s the limit, and with our combined expertise, we’re confident our collaboration will set new industry standards.

If you have a project or initiative where you need our help, please let us know.

Hello, to our Airship community!

As most of you know, 2023 marked a pivotal year for Airship as we joined forces with the esteemed Unosquare. But if you thought the news couldn’t improve, you’re in for a treat! We’re thrilled to announce that Unosquare has earned a place on the prestigious Inc. 5000 list for the eighth consecutive year!

Accomplishing this milestone is no small feat. Making the Inc. 5000 list once is impressive, but doing it for eight straight years is a testament to Unosquare’s unwavering commitment to excellence, innovation, and delivering top-notch services to its clientele.

But let’s get back to Airship for a moment. We’ve always prided ourselves on offering bespoke software development services tailored to meet each client’s unique needs and aspirations. By joining the Unosquare family, our mission becomes even more evident, and our resolve stronger. Together, we’re looking to propel the “Digital Product Development” sector into newer horizons.

Why is this partnership exciting for our clients?

Expanded Expertise: With Airship’s profound knowledge in crafting custom software solutions and Unosquare’s prowess in digital product development, our clients can now harness a broader spectrum of expertise.

Consistent Delivery of High-Quality Services: Airship and Unosquare have built reputations based on consistent quality and innovation. We’re set to create even more powerful, efficient, and reliable digital solutions.

Navigating the Digital Future, Together: The tech landscape is constantly evolving. But as a unified force, we’re more equipped than ever to help our clients navigate the waves of change confidently.

Now, more than ever, our commitment to our clients remains robust. We will continue crafting impeccable software solutions, ensuring Unosquare’s Digital Product Development services stay at the forefront of industry excellence. As Unosquare celebrates this incredible eight-year milestone, we can’t help but feel proud to be a part of this dynamic journey.

In closing, we extend our heartfelt congratulations to Unosquare for their astounding achievement. And to our cherished clients and partners – buckle up! With Unosquare and Airship at the helm, the digital skies are filled with endless possibilities.

Before the formal concept of feasibility studies became standard practice in software development, several activities were typically done, though less structured. 

Here’s what typically happened before feasibility studies:

1. Informal Discussions: Initial project ideas were often discussed informally among stakeholders, developers, and potential users.
2. Ad Hoc Requirements Gathering: Instead of systematically collecting requirements, developers or project leads would gather requirements based on discussions and their insights.
3. Prototyping: Some developers build prototypes or basic software versions to show stakeholders. This process allowed them to visualize the solution and offer feedback.
4. Intuition-based Decision Making: Decisions about whether to proceed with projects were often based on intuition, previous experience, or the perceived enthusiasm of stakeholders rather than systematic analysis.
5. Direct Implementation: In some cases, developers went directly to the coding and implementation phase based on preliminary discussions without formal project viability analysis.
6. Initial Cost Estimations: Rough estimations of costs were made, but these might have taken into account only some potential variables and risks.
7. Limited Market Research: Some market research was conducted, primarily if the software was intended for commercial sale. However, it might have needed to be more thorough than what’s included in a detailed feasibility study.
8. Trial and Error: Since there wasn’t a formal assessment like a feasibility study, there was a greater reliance on a “trial and error” approach. If a particular software solution wasn’t viable, it might be abandoned midway or after significant resources had already been invested.

The introduction of feasibility studies was an effort to formalize and bring structure to the early phases of software development. The shift towards formal feasibility studies in software development was primarily motivated by the need to minimize risks, ensure better allocation of resources, and improve the likelihood of project success. Feasibility studies provided a structured way to evaluate projects before significant resources were committed, making the software development process more predictable and efficient.

Why is a Feasibility Study Important in SDLC?

The feasibility study acts as a critical decision point in the Software Development Life Cycle (SDLC). Here’s why:

1. Risk Reduction: A feasibility study can highlight potential pitfalls and risks, enabling stakeholders to make informed decisions.
2. Resource Allocation: It ensures that resources, both time and money, are invested wisely in viable projects.
3. Clarity: Provides a clear understanding of the requirements and the potential challenges.
4. Stakeholder Confidence: Demonstrates due diligence to stakeholders, including investors.

Types of Feasibility Studies in SDLC

1. Technical Feasibility: Assesses whether the technical resources and capabilities, including hardware, software, and technical expertise, are available to complete the project successfully.
2. Economic Feasibility (Cost-benefit analysis): Evaluates the project’s financial viability by analyzing estimated costs against potential benefits.
3. Legal Feasibility: Reviews potential legal considerations, like copyright issues, patents, and data protection, and ensures that the proposed system doesn’t breach any regulations.
4. Operational Feasibility: Investigate if the proposed system can be integrated and operate within the existing organizational processes and structures.
5. Scheduling Feasibility: Determines whether the completion of the project will happen within the proposed time frame.

How Do You Conduct a Feasibility Study for Software Development?

1. Define the Scope: Clearly outline what the software project will achieve, including its functionality and features.
2. Gather Input: Engage stakeholders, subject matter experts, and potential users to gather relevant information.
3. Research & Analysis: For each type of feasibility (as mentioned above), gather data, and analyze. For instance, you’d evaluate available technology and expertise for technical feasibility.
4. Cost Estimation: Estimate the financial and human resources required for the project.
5. Document Findings: Present your findings, recommendations, and any potential challenges or risks.
6. Review & Feedback: Engage stakeholders for feedback and refine your study based on feedback.

Best Practices for a Feasibility Study

1. Engage Stakeholders Early: Get initial insights and buy-in from key stakeholders.
2. Stay Objective: A feasibility study should be neutral, presenting facts rather than being overly optimistic or pessimistic.
3. Use Accurate & Current Data: Outdated or incorrect data can lead to erroneous conclusions.
4. Consider Future Scalability: Even if the software solution meets current needs, consider its scalability for future requirements.
5. Seek Expert Opinions: Engaging experts can provide deeper insights, especially in technical and legal feasibility areas.
6. Regularly Update the Study: For long-term projects, updating the feasibility study can be crucial as the market, technology, and other factors evolve.

In the tech world, time is of the essence. With a thorough study, you’re not wasting precious weeks or even months on a project that’s not viable. It’s like having a time machine that shows you potential dead-ends so you can steer clear from the get-go. Nobody likes unpleasant surprises, especially not stakeholders or investors. When you can confidently present findings from a comprehensive feasibility study, it reassures them that their investment is grounded in solid research, not just hopeful thinking. 

An objective analysis tells you exactly where to deploy these resources for maximum impact, ensuring you’re not spreading yourself too thin or placing bets on the wrong horse. If you’re looking to nail your software project and bring it home with flying colors, a feasibility study isn’t just recommended; it’s essential. The prep work ensures your journey is smoother, faster, and more efficient, leading you straight to success. So, go ahead and invest that effort upfront.

Choosing Notifee

Push notifications are an important feature of mobile applications. They keep users engaged with an app over time. Finding a reliable package to integrate this feature on iOS and Android for React Native can be tricky. As phone software updates, many React Native packages become deprecated while more packages get added over time. This happened to my previous go-to package, react-native-push-notification, which recommended Notifee or react-native-notifications as a replacement.

I landed with Notifee as my go to push notifications package for a couple reasons. The ability to create repeating reminders and connect to Firebase Remote Notifications was needed. The creators Invertase, have made some great Firebase integrations with React Native and continue to support their packages long term.

Permissions

Before any notifications can be created, an app requires push notification permissions on the device. Notifee permissions require separate checks between the two platforms. The notifee.requestPermission function should request notification permissions for iOS and Android 13 or higher. Android 12 and earlier have this permission enabled by default unless a user explicitly turns it off. Android also requires a channel to assign the notification. I used the function below to return a Boolean value to check whether push notifications were allowed.

import { useCallback } from 'react'

import { Platform } from 'react-native';

import notifee, { AuthorizationStatus} from '@notifee/react-native';



const checkPermissions = async () => {

    if (Platform.OS === 'ios') {

      const settings = await notifee.requestPermission();

      return Boolean(

        settings.authorizationStatus === AuthorizationStatus.AUTHORIZED ||

          settings.authorizationStatus === AuthorizationStatus.PROVISIONAL,

      );

    }

    const settings =

      Platform.OS === 'android' && Platform.Version >= 33

        ? await notifee.requestPermission()

        : await notifee.getNotificationSettings();

    const channel = await notifee.getChannel('MyChannelID');

    return (

      settings.authorizationStatus === AuthorizationStatus.AUTHORIZED &&

      !channel?.blocked
    );

};

When a user wants to enable notifications, I would check this permissions value above to determine if I should navigate the user to the app permissions screen or turn notifications on in the app. 
To navigate the user to the correct permissions I have used this:

const enableReminders = async () => {

  const hasPermissions = await checkPermissions();

  if (hasPermissions) {

     // Enable push notification settings

  } else {

    Alert.alert(

      'Enable Notifications',

      'To receive notifications opt in from your Settings.',

      [{ text: 'Cancel' },{ text: 'Settings', onPress: openPermissionSettings}],

    );

  }

};



const openPermissionSettings = async () => {

  if (Platform.OS === 'ios') {         

    await Linking.openSettings();

  } else {

    await notifee.openNotificationSettings();

  }

};

Please note, these permission checks do not include Android’s AlarmManager API. This would require a different logical flow. You can find more details on iOS and Android permissions, respectively.

Separating System Permissions and App Settings

For a faster, simpler implementation, it is easier to let system permissions determine if push notifications are enabled; however, this forces the user to navigate out of the app each time they would like to re-enable push notifications. An additional check can be created to control whether push notifications are enabled or disabled within an app. Instead of relying on the permissions check, we need to think through these scenarios:

• If a user toggles notifications on in the app, make sure permissions are enabled. If so, enable them on the app. If not, direct them to the correct permissions, begin listening for the user to return to the app with React Native AppState, re-check permissions, and finally enable push notifications or dismiss depending on the settings granted.

• If a user toggles them off, disable the push notifications within the in-app settings.

• Make sure to check permissions on each active of the app, if ever gets disabled, disable the in-app settings as well.

Essentially, the permission and app settings must be enabled to add notifications. If permissions are removed, this also turns off the app settings. The benefit to this implementation allows the user to control notifications without needing to leave the app after permissions have been granted. 

Tying this together, I used this code in order to watch for permissions with AppState.

// App State hook watches for if the app is active

import React from 'react';

import { AppState, AppStateStatus } from 'react-native';



export const useAppState = () => {

  const [appState, setAppState] = React.useState<AppStateStatus>('active');

  React.useEffect(() => {

    const subscription = AppState.addEventListener('change', (nextAppState) =>

      setAppState(nextAppState),

    );

    return () => {

      subscription.remove();

    };

  }, []);



  return {

    appState,

  };

};

// Using app state to check permissions

const { appState } = useAppState();

const [watchAppStateToEnable, setWatchAppStateToEnable] = useState(false);



const openPermissionSettings = useCallback(async () => {

  if (Platform.OS === 'ios') {         

    await Linking.openSettings();

  } else {

    await notifee.openNotificationSettings();

  }

  setWatchAppStateToEnable(true);

}, []);



const checkAppStatePermissions = useCallback(async () => {

  const hasPermissions = await checkPermissions();

  if (hasPermissions && watchAppStateToEnable) {

    // Enable in-app push notification setting

  } else if (!hasPermissions) {

    // Disable in-app push notification setting

  }

  setWatchAppState(false);

}, [checkPermissions, watchAppStateToEnable]);



useEffect(() => {

  // Called each time the app is opened

  if (appState === 'active') {

    checkAppStatePermissions();

  }

}, [appState, checkAppStatePermissions]);

In this example, we need the watchAppStateToEnable value to only enable the notifications when the user is expecting to enable them. Otherwise, it matches device settings completely. This will also disable the setting if permissions are ever revoked. Disabling reminders is much easier. notifee.cancelAllNotifications will fully delete all Notifee notifications.

const disableAllReminders = async () => {

  // Disable in-app push notification setting

  await notifee.cancelAllNotifications();

};

The in-app push notification setting state may be stored however you like. Once you have this setup, you can use it to determine if notifications are enabled or disabled in the app. 

Valid Timestamp on Trigger Notification

Trigger notifications allow users to schedule out notifications at specific timestamps or intervals.

At first, the timestamp required for creating trigger reminders tripped me up. The value just needs to be in the future from the current time. I highly recommend adding the package dayjs as it has makes handling dates in js much easier to implement.

For daily reminders, I added this condition to secure a valid timestamp for a repeating reminder from a date-picker. If the timestamp has already passed, it simply targets the selected time for tomorrow. The second(0) is added for the notification to show at the beginning of the selected minute. If a user wants to show a notification weekly, .add(1, ‘week’) would also work. 

const validTimestamp =

        dayjs(timestamp).second(0).valueOf() > new Date().getTime()

          ? dayjs(timestamp).second(0).valueOf()

          : dayjs(timestamp).add(1, 'day').second(0).valueOf();

Utility Function

I created this utility function to make creating trigger notifications easier. This was created to suit my needs but can easily be customized. Please note creating many trigger notifications with iOS media attachments may affect app performance.

import notifee, { RepeatFrequency } from '@notifee/react-native';



type NotifeeTriggerReminder = {

  title: string;

  body: string;

  timestamp: number;

  id?: string;

  image?: string;

  repeatFrequency?: RepeatFrequency;

};



const setupNotifeeTimestampReminder = async ({ id, title, body, timestamp, image, repeatFrequency }: NotifeeTriggerReminder) => {

      const idContent = id ? { id } : {};

      const iOSMedia = image ? { attachments: [{ url: image }] } : {};

      const androidMedia = image

        ? {

            style: {

              type: AndroidStyle.BIGPICTURE,

              picture: image,

            } as AndroidBigPictureStyle,

          }

        : {};

      await notifee.createTriggerNotification(

        {

          ...idContent,

          title,

          body,

          android: {

            channelId: ChannelId,

            smallIcon: 'ic_small_icon',

            pressAction: {

              id: 'default',

            },

            ...androidMedia,

          },

          ios: {

            sound: 'default',

            ...iOSMedia,

          },

        },

        {

          repeatFrequency,

          timestamp,

          type: TriggerType.TIMESTAMP,

        },

      );

    };

Firebase Cloud Messaging

Notifee interacts well with Firebase Cloud Messaging and provides plenty of documentation. Remote notifications handled in the foreground and background are handled separately, but both need to be displayed. I added this utility function for both instances in and outside of the app. 

import notifee from '@notifee/react-native';

import { FirebaseMessagingTypes } from '@react-native-firebase/messaging';



export const onRemoteMessageReceived = async ({

  notification,

  messageId,

}: FirebaseMessagingTypes.RemoteMessage) => {

  if (notification) {

    try {

      await notifee.displayNotification({

        id: messageId,

        title: notification.title,

        body: notification.body,

        android: {

          channelId: 'ChannelID',

          smallIcon: 'ic_small_icon',

          pressAction: {

            id: 'default',

          },

        },

        ios: {

          sound: 'default',

        },

      });

    } catch (e) {

      // Report Error

    }

  }

};

To receive notifications while the app is in the background, I added this function above the AppRegistry on the index.js file. On Android, adding the utility function created a duplicated notification bug. To prevent a duplicated push notification, I am only calling the utility function on iOS. 

import { AppRegistry, Platform } from 'react-native';
import messaging from '@react-native-firebase/messaging';

import { onRemoteMessageReceived } from './app/utils/onRemoteMessageRecieved';



messaging().setBackgroundMessageHandler(

  Platform.OS === 'ios' ? onRemoteMessageReceived : () => Promise.resolve(),

);

And then to display foreground events, I added a similar function to the App.tsx file.

useEffect(() => {

    const unsubscribe = messaging().onMessage(onRemoteMessageReceived);

    return unsubscribe;

}, []);

Limitations and Workarounds

Here are a couple of limitations I have come across using Notifee and ways to work around them. 

One bug on recently updated Android 13 devices may cause the app to crash. If a user creates scheduled trigger reminders on Android 12 or earlier and then updates their device to Android 13, notifee.getTriggerNotifications throws an error that needs to be handled. To bypass this, I am clearing all scheduled notifications with await notifee.cancelAllNotifications() one time on all Android 13 devices. 

One limitation prevents delaying a repeating reminder on iOS. For example, I have an app with daily objectives. The app should remind users everyday unless the objective has already been completed. I originally planned to reschedule a daily repeating reminder if the objectives were completed. This works on Android but shows every day regardless on iOS. 

As a workaround, I added weekly repeating reminders. On app load, these reminders all get recreated. After completing the objective, I am removing the reminder for that day of the week. It is not a perfect solution, but in this case this works fine.

const scheduleRepeatingReminder = async (timestamp: number) => {

      const week = new Array(7).fill('');

      for await (const [index, _day] of week.entries()) {

        const dayTimestamp = dayjs(timestamp).add(index, 'day').second(0).valueOf();

        const validTimestamp =

          dayTimestamp > new Date().getTime()

            ? dayTimestamp

            : dayjs(dayTimestamp).add(1, 'week').valueOf();

        await setupNotifeeTimestampReminder({

          id: dayjs(validTimestamp).format('ddd'),

          title: 'Reminder',

          body: 'This is a reminder',

          timestamp: validTimestamp,

          repeatFrequency: RepeatFrequency.WEEKLY,

        });

      }

    };



  const removeRepeatingReminder = async () => {

    const reminderId = dayjs().format('ddd');

    await notifee.cancelTriggerNotification(reminderId);

  };

Using Notifee to integrate push notifications within an app can really enhance user engagement. This package provides a flexible, reliable approach for adding notifications to both iOS and Android with React Native. Thank you for taking the time to read this, if you have any suggestions or questions, please let us know!

Ruby on Rails, commonly known as Rails, is a robust web application framework written in the Ruby programming language. It was created by David Heinemeier Hansson and released in 2004. Rails follows the Model-View-Controller (MVC) architectural pattern, which provides a structured approach to building web applications.

Ruby on Rails is a popular web application framework that allows developers to build robust, scalable, and maintainable web applications quickly, thanks to its convention-based approach and the wealth of available libraries. Whether you’re a seasoned developer or just starting, Rails can be a fantastic tool to bring your web projects to life!

So, what can you do with Ruby on Rails? Well, it’s mainly used for developing web applications, whether simple websites or complex platforms. Rails come with many handy built-in tools and conventions, making it a favorite choice for developers aiming for productivity and efficiency.

Something notable about Ruby on Rails is its “convention over configuration” philosophy. It means that Rails assumes certain things about your application, and as long as you follow these conventions, you’ll have to write less code and get things done faster. Less code and speed make getting a project up and running easy.

Rails also promotes “gems,” which provide extra functionality to your application. With the vast collection of community-contributed “gems,” you can easily add features like authentication, data visualization, or payment processing without reinventing the wheel.

Is Ruby on Rails front-end or back-end?

Ruby on Rails is primarily a back-end web application framework. It focuses on handling the server-side aspects of web development, managing the application’s logic, data processing, and communication with databases. As mentioned earlier, Rails follows the Model-View-Controller (MVC) architectural pattern, which separates the application’s data, presentation, and user interface concerns.

However, while Rails is predominantly a back-end framework, it also provides some front-end capabilities. It allows developers to integrate front-end technologies like HTML, CSS, and JavaScript to create dynamic and interactive user interfaces. Rails has built-in support for working with these front-end technologies, making it a full-stack web development framework.

How difficult is it to learn Ruby on Rails?

Learning Ruby on Rails can be a rewarding and enjoyable experience, especially if you’re already familiar with the Ruby programming language. Rails emphasizes developer productivity and follows the “convention over configuration” principle, which provides sensible defaults and reduces the code you need to write. The difficulty of learning Ruby on Rails depends on your background, preferences, and the specific projects you’re working on.

Compared to common languages like Python and Java, the difficulty of learning Ruby on Rails can vary depending on your prior programming experience and familiarity with the respective languages. Let’s break it down:

1. Ruby on Rails vs. Ruby: If you already know Ruby, diving into Rails will be relatively straightforward. Rails build on the Ruby language, so you’ll find many familiar concepts. If you’re new to Ruby, you should spend some time grasping the language first before jumping into Rails.
2. Ruby on Rails vs. Python: Rails and Python’s web frameworks, like Django or Flask, have their strengths. Rails has more built-in conventions and is well-suited for rapidly developing web applications. On the other hand, Python has a simpler and more versatile syntax, making it approachable for beginners.
3. Ruby on Rails vs. Java: Java is a statically-typed language, requiring more code than Ruby’s dynamically-typed nature. Rails, a framework built with developer productivity in mind, can generally lead to faster development than Java-based web frameworks. Java might have a steeper learning curve due to its verbosity.

What big tech companies use Ruby on Rails?

Several notable companies in the technology industry embrace Rails for building their web applications. Some of these companies include:

1. GitHub: the popular code hosting platform, GitHub started as a Ruby on Rails application. It later expanded its tech stack, but Rails played a crucial role in its early development.
2. Airbnb: Airbnb, the online marketplace for lodging and vacation rentals, used Ruby on Rails in its early stages to quickly build and iterate on its platform.
3. Shopify: Shopify, the e-commerce platform, also started with Ruby on Rails and leveraged its rapid development capabilities to become a significant player in the e-commerce industry.
4. Hulu: The video streaming service was initially built on Ruby on Rails, which helped the company scale and deliver content to millions of users.
5. Basecamp: Basecamp, a project management and team collaboration tool, was created by the creator of Ruby on Rails, David Heinemeier Hansson. It serves as an excellent showcase of what Rails can do.
6. SoundCloud: SoundCloud, the popular audio distribution platform, used Ruby on Rails to build its initial versions and quickly gain traction in music-sharing.
7. Twitch: In its early days, the live streaming platform Twitch utilized Ruby on Rails to establish its presence in the gaming and content creation community.
8. Zendesk: Zendesk, the customer service and support software provider, adopted Ruby on Rails for its flexible and fast development capabilities.

While some of these companies have since expanded their tech stacks or introduced new technologies, their early adoption of Ruby on Rails highlights the framework’s ability to kickstart projects quickly and efficiently, making it a preferred choice for startups and companies looking for agile development in the technology industry.

What are some advantages and disadvantages of using Ruby on Rails?

Advantages:

1. Rapid Development: Ruby on Rails embraces the “convention over configuration” philosophy, providing sensible defaults and reducing the amount of boilerplate code. This philosophy accelerates the development process, allowing you to build web applications quickly.
2. Developer-Friendly: Ruby, the programming language used in Rails, has a clear and expressive syntax. The syntax makes the codebase easy to read and maintain, increasing developer productivity and satisfaction.
3. Rich Ecosystem: Rails has a vast collection of community-contributed gems (packages) that add extra functionality to your application. This extensive ecosystem allows you to leverage pre-built solutions, saving time and effort.
4. Scalability: While Rails is well-suited for rapid development, it can also handle scalability. Many successful startups have started with Rails and scaled their applications to meet increasing demands.
5. Active Community: Ruby on Rails has a vibrant and active community of developers, which means you can find plenty of tutorials, resources, and support to help you along your development journey.

Disadvantages:

1. Performance: While Rails is efficient for many applications, there may be better choices for highly-traffic, performance-critical applications. The framework’s convention-based approach can sometimes lead to performance bottlenecks.
2. Learning Curve: If you’re new to Ruby or web development, the learning curve for Ruby on Rails can be steeper than other frameworks. Understanding the framework’s conventions and best practices might take some time.
3. Maintenance: As an application grows, maintaining the codebase might become challenging. With proper architecture and organization, Rails applications can become easier to keep in the long run.
4. Limited Flexibility: While Rails’ conventions can be a boon for productivity, they might limit the flexibility for specific projects with unique requirements. Deviating from the conventions may lead to more complexity.
5. Scalability Challenges: While Rails can handle scalability for many applications, extremely high-scale projects might face challenges as the application grows. Proper optimization and architecture planning are essential.

Ruby on Rails offers many advantages in rapid development, developer-friendliness, and a rich ecosystem. However, there might be better fits for some projects, especially regarding performance-critical applications or those with particular requirements. Weighing the pros and cons will help you determine if Ruby on Rails is the right choice for your web development needs.

From improving medical diagnoses to AI powered wearables, the adoption of AI in healthcare is advancing medical treatment, patient experiences, and helping clinics and hospitals run more efficiently. In this article, we’ll look at some of the applications and companies leading innovation in healthcare and life sciences.

Artificial Intelligence in Improving Medical Diagnosis

Medical errors are one of the leading causes of death in the United States. From incomplete medical records to natural human error, one of AI’s most exciting healthcare applications is helping to improve the diagnostic process. In fact, according to an MIT study, 75% of medical staff who have AI agree that it has enabled better predictions in the treatment of disease. Here are a couple of application examples that are able to predict and diagnose diseases quickly using the power of AI.

Regard

The healthtech startup Regard uses AI technology to diagnose patients. The company describes its automated system to be the “clinical co-pilot” to electronic medical records (EMRs). The data from EMRs is synthesized to discover a diagnosis. Additionally, healthcare providers receive specific recommendations about patient care. The system also updates patient documents automatically to reduce burnout among healthcare workers. For a look into how Regard’s AI co-pilot works, check out this demo video.

Enlitic

Enlitic develops deep learning medical tools to streamline radiology diagnoses. The company’s deep learning platform analyzes unstructured medical data — radiology images, blood tests, EKGs, genomics, patient medical history — to give doctors better insight into a patient’s real-time needs. Checkout this video that dives a little deeper.

Freenome

Did you know that there are over 100 different types of cancer and the biological signals indicating the presence of those cancers can vary widely? Freenome uses AI in screenings, diagnostic tests and blood work to test for cancer. The Freenome platform consists of three powerful components (below). By deploying AI at general screenings, Freenome aims to detect cancer in its earliest stages and subsequently develop new treatments.

Artificial Intelligence in Clinical Trials Pharmaceuticals

Testing new drugs is a slow and expensive process. Around 80% of clinical trials fail to meet enrollment timelines, and around one-third of Phase III clinical studies are terminated because of enrollment difficulties. Artificial intelligence-powered technology has the potential to change every stage of the clinical trials process, from finding a trial to patient enrollment to medication adherence. Here are three companies applying AI to revolutionize the fragmented clinical trials process.

Deep 6

Deep 6 AI uses artificial intelligence and natural language processing on clinical data to find eligible patients for clinical trials. Its software accelerates patient recruitment and getting life-saving treatment to patients. Their technology creates dynamic, holistic patient views — what they call patient graphs. These graphs provide broader clinical context and truly allow patient characteristics to be precision matched to trial criteria, resulting in fewer false positives and less wasted time.

Owkin

Owkin leverages AI technology for drug discovery and diagnostics with the goal of enhancing cancer treatment. The company’s AI tools help identify new drug targets, recommend possible drug combinations and suggest additional diseases that a drug can be repurposed to treat. Owkin also produces RlapsRisk, a diagnostic tool for assessing a breast cancer patient’s risk of relapse, and MSIntuit, a tool that assists with screening for colorectal cancer. Here’s a video with the Owkin Chief R&D Officer, Jean-Philippe Vert, explaining how Owkin uses cutting-edge causal AI and patient data to advance precision medicine for patients.

Artificial Intelligence In Improving the Patient Experience 

There’s no question that the COVID-19 pandemic greatly accelerated the use of digital health in areas such as public health surveillance and virtual care, highlighting some of the many ways in which digital health can strengthen and enhance health care planning and delivery. The ability to provide an efficient patient experience, especially online, enables clinics and hospitals to treat as many patients as they can. Here are two examples of how AI is helping better manage patient flow and care.

Walgreens

Walgreens leverages artificial intelligence (AI) in both internal- and external-facing areas of its enterprise operations.  Their Digitate AIOps solution helped to streamline both the COVID-19 vaccine scheduling process for customers and helped manage the tech support tickets from its IT department. One of the challenges for Walgreens during the height of the pandemic was making sure they could provide the right information to their customers as to which pharmacies would be open. “Predicting or telling our customers when a store would be open and when the pharmacy would be available in the store suddenly became more difficult. The usage of the AIOps solution was really about making that information available in real-time. As we were learning the situation on the ground across all 9,000 stores, this information about stores and hours of operation could be updated in a timely fashion,” Yael Gomez, VP, Global IT, Integration and Intelligent Automation at Walgreens.

Mayo Clinic

The Mayo Clinic is applying AI to electrocardiogram (ECG) data captured by smartwatches. They developed an iPhone app that uses ECG data to identify patients with weak heart pumps. “The ongoing AI research in cardiology is part of Mayo’s commitment to bringing a digital transformation to health care. Advanced diagnostics that once required travel to a clinic can be accurately done, as this Apple Watch ECG study demonstrates, from a patient’s wrist whether they live in Brazil or Baton Rouge. App-based access to a medical center can help address health disparities by making high-level diagnostics accessible to more people in real time,” says Bradley Leibovich, M.D., medical director of Mayo Clinic’s Center for Digital Health.

According to Forbes, 70% of financial firms are using machine learning to perform things like cash flow predictions, adjust credit scores, and detect fraud. In fact, the market value of AI in finance was estimated to be $9.45 billion in 2021 and is expected to grow 16.5%  by 2030. 

In this article, we uncover the applications, benefits and impact AI is having on financial services.

Artificial Intelligence in Financial Credit Decisions

AI solutions are helping  credit lenders and banks make smarter underwriting decisions by using various factors that more accurately assess traditionally underserved borrowers in the credit decision making process. 

Here are some companies who are revolutionizing the underwriting process:

Ocrolus

Ocrolus offers document processing software that combines machine learning with human verification. Ocrolus’ software analyzes bank statements, pay stubs, tax documents, mortgage forms, invoices and more to determine loan eligibility, with areas of focus including mortgage lending, business lending, consumer lending, credit scoring and KYC.

DataRobot

DataRobot enables Financial Services companies to automate the painful pieces of the ML lifecycle, giving data science teams the time and tools to focus on business impact. Institutions that use DataRobot can better understand, govern, and evaluate their models, find investment opportunities quickly, expand their portfolios, and nimbly respond to rapidly changing market conditions.

Zest AI

Zest AI is an AI-powered underwriting platform that helps companies assess borrowers with little to no credit information or history. Using more data, better math, and smarter software, lenders can safely expand credit access through more accurate risk prediction, faster credit decisions, and more inclusive lending.

Artificial Intelligence in Improving Predictions & Managing Risk 

Financial experts are turning to machine learning to more accurately  pinpoint trends and identify risks in order to make more informed decisions for businesses. Here are a couple of companies that are using artificial intelligence in finance to help banking institutions improve predictions and manage risk more efficiently. 

Simudyne

Simudyne’s platform allows financial institutions to run stress test analyses and test the waters for market contagion on large scales. The company offers simulation solutions for risk management as well as environmental, social and governance settings. Simudyne’s secure simulation software uses agent-based modeling to provide a library of code for frequently used and specialized functions.

SymphanyAI

SymphonyAI Sensa-NetReveal provides financial crime, risk management and fraud detection and prevention across banking, financial markets, and insurance. Their suite of Unauthorised Trading and Anti-Money Laundering solutions are specifically designed to support capital markets customers.

Artificial Intelligence in Personalized Banking

As of 2022, 78% of adults in the U.S. prefer to bank via a mobile app or via a website. Only 29% of Americans prefer to bank in person. AI assistants, like chatbots, use AI to generate instant customer service and personalized financial advice.

Here are  two companies using AI to learn from customers and create a better banking experience.

Trim

Trim is a money-saving assistant that connects to user accounts and analyzes spending. The smart app can cancel money-wasting subscriptions, find better options for services like insurance, and even negotiate bills. According to a 2021 Finance Buzz article, trim has saved more than $20 million for its users.

Ally Assist

Ally Assist is the virtual assistant in Ally Financial’s mobile banking application. Ally Assist is both text and voice-enabled, meaning users can simply speak or text with the assistant to take care of their banking needs. Ally Assist also has the ability to predict customer needs by analyzing accounts and transactions to present context-aware topics and messages to customers.

Artificial Intelligence in Fraud Detection

Cybersecurity and fraud detection efforts are an absolute necessity for any bank or financial institution. AI plays a key role in improving the security for users, helping to prevent hackers and identity thieves from accessing bank accounts and personal information.

Here are some companies striving to make mobile and online banking safer and more reliable.

Feedzai

Feedzai is a software company that offers end-to-end fraud-fighting and anti-money laundering solutions to retail banks. Using machine learning and risk management tools, Feedzai provides banks and their customers with multi-channel fraud protection for issues like account takeover, transaction fraud and new account verification.

Vectra

Vectra offers an AI-powered cyber-threat detection platform, which automates threat detection, reveals hidden attackers specifically targeting financial institutions, accelerates investigations after incidents and even identifies compromised information.Unlike other artificial intelligence that simply detects anomalies and requires constant input from analysts, Vectra AI prioritizes what’s urgent for each environment. Analysts can focus on what actually matters to stop ransomware and other attacks that cause the most damage — in record time.

Darktrace

Darktrace’s AI, machine learning platform analyzes network data and creates probability-based calculations, detecting suspicious activity before it can cause damage for some of the world’s largest financial firms. Bank One implemented Darktace’s Antigena Email solution to stop impersonation and malware attacks, according to a case study. The bank saw a rapid decrease in email attacks and has since used additional Darktrace solutions across its business.

How do I start a SaaS business?

Creating a SaaS company requires careful planning and execution. Here are the key steps to get you started:

1. Identify a Problem: Start by identifying a specific problem or need that can be solved through Software. Research your target market to ensure there is a demand for your solution.
2. Market Analysis: Conduct a thorough market analysis to understand your competition, target audience, and potential customers. Determine the unique value proposition that sets your SaaS product apart.
3. Define Your Product: Clearly define the features and functionalities of your SaaS product. Determine how it will solve the identified problem and benefit your target audience.
4. Build a Minimum Viable Product (MVP): Develop an MVP that showcases the core functionality of your product. An MVPP lets you demonstrate the base elements of your Software, gather feedback, validate your idea, and iterate on the product.
5. Develop the Software: Once you have secured funding, assemble a team of skilled developers and designers to develop the full version of your SaaS product. Ensure you follow agile development methodologies for efficiency and flexibility, then conduct rigorous testing to fix bugs and ensure a seamless user experience.

How much does it cost to set up SaaS?

When setting up a SaaS business, understanding the costs involved is crucial for effective financial planning. Here are some key factors to consider:

1. Development Costs: Developing a robust and feature-rich SaaS product requires skilled professionals such as software developers, designers, and quality assurance specialists. The cost of hiring these experts varies depending on their experience and location. The complexity of your product and the time required for development will impact the overall cost. Creating a detailed project plan and estimating the development costs with a scope in mind is advisable. At Airship, we can walk you through each stage in our Discovery process. 
2. Infrastructure Costs: SaaS applications typically require robust and scalable infrastructure to handle user demand. This infrastructure will likely include servers, storage, databases, and networking components. Cloud service providers, such as Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform, offer scalable infrastructure solutions that allow you to pay for what you use. 
3. Software Licensing and Tools: Depending on your product requirements, you may need to invest in software licenses and development tools. These costs include operating systems, development frameworks, project management software, version control systems, and various productivity tools. Consider both upfront costs and ongoing subscription fees when estimating your budget.
4. Marketing and Customer Acquisition: Acquiring customers and establishing your brand presence requires practical marketing efforts. Filling your sales funnel includes digital marketing campaigns, content creation, social media management, search engine optimization (SEO), and advertising. 
5. Ongoing Maintenance and Support: After launching your SaaS product, maintenance and support are vital to keep it running smoothly. Post-launch, attend to bug fixes, software updates, security patches, and customer support. Plan for the costs of maintaining and improving your product based on user feedback and evolving market needs.
6. Legal and Compliance: Ensure you allocate a budget for legal services, such as incorporating your business, drafting contracts, and protecting your intellectual property. Additionally, consider compliance requirements, such as data protection regulations (e.g., GDPR or CCPA), and budget for any necessary audits or certifications.

It’s important to note that the cost of setting up a SaaS business can vary significantly. While some entrepreneurs may bootstrap their initial development and start with a minimal budget, others may seek external funding to cover development, marketing, and operational costs. Consider your unique requirements, long-term growth plans, and available resources when estimating your budget.

Are SaaS businesses profitable?

SaaS businesses have the potential to be highly profitable. Their subscription-based revenue model, recurring payments, and scalability make them attractive for long-term profitability. Success is not guaranteed. Factors such as market competition, customer acquisition costs, customer retention, and pricing strategy determine profitability. Focus on value, retaining customers, and continuously improving your product to maximize profitability.

What are a few things you should remember while creating a SaaS company?

When creating a SaaS company, it’s essential to consider the following:

1. Customer-Centric Approach: Understand your customers’ pain points and design your product to address their needs effectively. Regularly gather feedback and make continuous improvements based on user insights.
2. Scalability and Infrastructure: Build your Software with scalability in mind. As your customer base grows, your infrastructure should be able to handle increased demand. Utilize cloud-based hosting services to accommodate scalability and provide a seamless experience to users.
3. Security and Data Privacy: Prioritize the security of your customers’ data. Implement robust security measures like encryption, access controls, and regular security audits. Comply with data protection regulations like GDPR or CCPA to build customer trust.
4. Customer Success and Support: Provide exceptional customer support to ensure customer satisfaction and retention. Establish a robust customer success team that can assist users, address their concerns, and guide them in maximizing the value they get from your product.

How do I start a SaaS company with no software experience?

Starting a SaaS company with prior software development experience is challenging but possible. Here are a few steps to help you overcome the lack of knowledge:

1. Learn and Educate Yourself: Learn about the SaaS industry, business fundamentals, and best practices. Read books, attend industry events, and connect with experienced professionals who can provide guidance.
2. Collaborate with Experts and Mentors: Partner with skilled individuals with SaaS industry experience. These stakeholders may be co-founders, advisors, or consultants who can offer guidance and bridge the knowledge gap.
3. Leverage Existing Platforms: Utilize existing SaaS platforms and tools to build your product to save development time and costs while leveraging the expertise of established media.

Starting a SaaS company is an exciting and challenging endeavor. By following the steps outlined above, conducting thorough market research, and being customer-focused, you can increase your chances of success in this competitive industry. Even if you lack experience, seeking guidance and leveraging existing resources can help you overcome financial and development obstacles.

At TeamAirship.com, we understand the intricacies of building bespoke Software for SaaS companies. With our expertise in developing scalable and secure SaaS solutions, we can help turn your vision into reality. Visit www.teamairship.com to learn more about how we design, build and enhance custom software solutions and how we can assist you in creating a successful SaaS product for your business.