Development

Native and Cross-Platform Development: Weighing the Pros and Cons

September 26, 2023

David Zadražil

CTO

In app development, two roads diverge: native and cross-platform development. Each comes with its own set of advantages and trade-offs, impacting an app's performance and reach. Native development is like tailored precision for specific platforms, while cross-platform promises versatility. Keep reading to navigate the intricacies and choose the optimal route for your development journey.

Native development is like tailoring a suit specifically for a single occasion – iOS or Android. You craft the code using platform-specific tools like Swift or Java, ensuring it fits perfectly. The perk? Your app performs like a champion because it's optimized for that one platform, utilizing all the latest features and tools available.

Cross-platform development is more like having a versatile outfit that looks good on various occasions. You create a single set of code that smoothly runs on different platforms, be it iOS, Android, or Windows. This trend is on the rise due to its cost-effectiveness, speedy development cycles, and easier maintenance across the board. Think about it: one update, and it applies everywhere, maintaining consistency and minimizing hiccups.

Pros and Cons of Native Development

Native development offers clear advantages that contribute to peak app performance. Through a tailored approach for a single platform, apps achieve exceptional optimization and responsiveness. This method guarantees smooth integration with operating systems, delivering a good user experience via the latest features and APIs. Swift adoption of new platform features is another perk, ensuring timely access to advanced functionalities.

However, these benefits do bring certain considerations. Native development necessitates separate codebases for each platform, which results in higher costs and extended development schedules compared to cross-platform alternatives. Crafting platform-specific code can be intricate and pose challenges for those less acquainted with varied platforms. The distinct App Store approval processes for each platform further add complexity, as developers must manage separate reviews.

Notwithstanding these limitations, native development remains the preferred choice for apps prioritizing performance and advanced features. Choosing between native and cross-platform development requires carefully considering these factors in relation to the project's needs and limitations.

Pros and Cons of Cross-Platform Development

Cross-platform development offers valuable benefits for efficient app creation. Developers can write code once and apply it across various platforms, saving time and resources. Building a single app for various platforms is cost-effective and reduces expenses compared to separate development.

Maintenance is streamlined as cross-platform apps share a common codebase, simplifying updates. Tools like Xamarin and Race Native accelerate development, making cross-platform development an attractive option for swift app creation.

However, challenges arise. Performance can be compromised due to shared code impacting speed. Platform-specific features are limited, affecting functionality and user experience. Compatibility issues across devices may surface, requiring meticulous troubleshooting. Regardless, cross-platform development remains a practical choice for businesses that prioritize efficiency and cost-effectiveness, given its benefits align with their objectives.

Choosing the Right Approach

Selecting the ideal development approach for your project demands careful deliberation across various aspects. The factors like project requirements, timeline, budget, and target audience play pivotal roles in guiding your decision. Here are fundamental considerations to keep in mind:

Project Requirements: If leveraging the latest platform features and APIs is a priority, native development may hold the advantage. Conversely, if you seek code reusability across platforms, cross-platform development could be the optimal path.

Timeline: If time is tight, cross-platform development proves efficient. However, for a blend of performance and deep OS integration, native development takes precedence.

Budget: Native development frequently involves higher costs due to platform-specific codebases. Meanwhile, cross-platform development offers cost-effectiveness by covering multiple platforms with one codebase.

Target Audience: Tailoring to a specific platform's audience favors native development, enhancing performance and user experience. Yet, for broad outreach across platforms, cross-platform development provides adaptability.

Balancing Factors for Smooth Development

Considering these factors helps you to choose a path aligned with your project's aspirations. While switching from one approach to another is possible, it can entail substantial effort, time, and cost. The extent of these factors depends on your project's complexity and the technologies involved. Opting for the correct approach from the outset is advisable to circumvent the necessity of transitioning down the line.

Struggling to make the right choice? At Cleevio, we excel in steering businesses through the development journey. Whether it's native or cross-platform, our experts adeptly navigate the intricacies to help you select the optimum path for your project.

Contact us today to ensure your app's success.

What’s next?

Let’s continue the conversation.

3D representation of discovery track, glass cubes and a metal arrow that spins around them.

Stay in touch

Thank you! We will be in touch.

Oops! Something went wrong while submitting the form.

Project

1 min read

Pivot Like a Pro: Startup Strategies for Success

Cleevio

Company News

Discover the highlights from our recent exclusive panel discussion featuring Roman Stanek, CEO of GoodData, alongside industry leader Milo Poplar and our Head of North America, Filip Orth.

The event provided valuable insights into global-scale product building and entrepreneurial success. Dive into the key takeaways and memorable moments from this engaging discussion, where experienced pioneers shared their wisdom and expertise on the AI landscape.

We were thrilled to have Roman Stanek and his impressive track record in building successful startups. His journey began with the acquisition of NetBeans by Sun Microsystems in 1999, followed by the acquisition of Systinet by Hewlett Packard in 2006. Along the way, his ventures received support from renowned VC funds like a16z, Intel Capital, and General Catalyst.

Outsourcing

During the event, our discussions delved deeply into the strategies startups can employ to enhance efficiency through outsourcing across various operational domains. We explored how outsourcing can serve as a vital tool in mitigating the challenges inherent in the dynamic startup landscape. Among others, these challenges encompass navigating a tough fundraising environment and contending with fierce competition in virtually every industry.

Agility and adaptability

Central to our discussions was the imperative for startup founders to remain agile and adaptable in the face of evolving circumstances. We underscored the critical importance of being responsive to market shifts and customer demands, emphasizing the need for continual adjustment to ensure the longevity and success of their ventures.

Operational effectively

The ability to pivot effectively is essential, particularly when considering the quest for operational efficiency. In this context, leveraging outsourcing capabilities becomes paramount, whether it is in technological development, sales, marketing, or legal compliance. This strategic approach is especially pertinent in the current landscape, where fundraising endeavors are meeting with increased difficulty, and access to capital is more constrained than it was just two years ago.

Milo Poplar, Co-founder of Eldison during presentation

We intend to make this event a regular occurrence. We aim to host Founders’ Lounge regularly, each time focusing on a different theme and bringing in a special guest who will share insights from their entrepreneurial journey.

Are you a founder, investor, CTO or decision-maker in the technological startup environment seeking to accelerate your growth and gain a competitive edge in the market? Watch our LinkedIn for future invites!

Development

1 min read

Crash-Proofing Your Code: Setting Up Sentry on Android

Tomáš Dvořáček

Senior Android Developer

Welcome back! As promised, we are here with the second part of the Crash-proofing series. This time, we will show you how to set up Sentry for the Android platform and some nice-to-have stuff as a bonus.

Let's begin!

Create sentry.properties file inside your Android project’s root folder

Initial setup in Sentry Admin

These are a few things you need to do before implementing Sentry Android SDK.

Create a new project in Sentry. Give this project some appropriate name like your-project-android
Then go to Settings → Projects → Your new Project → General Settings

You should see the name of your project. This is your project_id. In sentry.properties, replace <project_id> with it
Then go to Organization settings → General Settings, copy your organisation_slug and replace <organisation_slug> inside sentry.properties

Then go to User and tokens and create new Token. You can add every permission to it for a start but its better to check every permission and decide for yourself what is needed.

Then copy your new auth token and replace <auth_token> with it inside sentry.properties.Sentry can upload ProGuard mapping files for you and needs this auth token. Ignore this if you don’t care about ProGuard
Your sentry.properties should be filled now.
Then go to Settings → Projects → Your new Project → Client Key (DSN)
Get your DSN link and save it somewhere for now.

Now you can return to your Android Project

Adding sentry to project

A full tutorial is on this page. Sentry can set itself with a command, but if you prefer a manual approach or have problems, follow the instructions below or this page. Sentry will also give you a direct link for setup in Android Studio (https://sentry.io/organizations/XXX/projects/YYY/getting-started/)

Add this to your main module build.gradle

Open your application class and initiate Sentry

Let’s explore what each line does:

This line applies the environment to the issue. If you use several build flavors like development and production, you can then easily filter specific flavors.

These lines set the percentage value of how many traces to log. 100% means everything is logged. It’s not recommended to collect everything in a production environment; however, e.g., on development, it’s a good thing since testers could find bugs. In our example, we set the percentage on the release version to 10%.

Open your AndroidManifest.xml file inside your main module and insert this

If you don’t want to use CI/CD and just hardcode your DSN, replace ${sentryDsnUrl} with your collected DSN link.

Open app’s build.gradle and setup DSN there as well

Add Sentry gradle plugin to project

This code enables sentry gradle plugin. This prepares scripts for your convenience like uploading aab to sentry with proguard mapping files.

Nice things to know

Assign someone to new issue

Every issue in Sentry can be assigned to someone and you can do that manually or automatically with rules.

Create Jira issue directly from Sentry

If you setup the Jira integration mentioned in the previous article, Sentry enables you to quickly and easily create Jira issues from the issue itself.

Discover page

Discover page let’s you quickly query in all yours collected data so you can answer analytics questions or analyse potential health issues in your project. You can use predefined queries or create, edit and delete your own queries. It’s really powerful tool but it’s limited only to Trial and Business Plan.

Pluggins for Sentry

Sentry for Android offers plugins which let’s you automatically collect more specific data. For example:

Some stuff like Android Fragments, okHttp events and logcat are already logged automatically from Sentry version 3.1.0.

In order to disable them, change the sentry config in the project’s build.gradle.

OkHttp plugin

Like said above, from Sentry 3.1.0, Sentry will automatically log OkHttp event via manipulating your final bytecode and inserting SentryOkHttpInterceptor. This will create breadcrumbs which would look like this:

‍

If you use Sentry 3.11.0+, Sentry will also insert SentryOkHttpEventListener which will log even more data from http requests. Everything will be logged with logcat:

Thank you for diving into the second part of our series. If you have any questions, feel free to catch up or reach out.

‍

#meetcleevio

1 min read

From Code to Culture: The Backbone of Our Backend Team

Přemysl Rucký

Backend Lead

Hey there! Curious about what makes our backend team tick? Let me spill the beans on what keeps us running at Cleevio.

Team Contract: Our Secret Sauce

Ever heard of a team contract? It's like our BE team's rulebook but cooler. We all chipped in to create this gem, covering everything from our core values to nifty Slack etiquettes (like no-reply expectations after 4 PM). It's not just a newbie guide; even our weathered developers learn a thing or two from it.

Bringing the Team Together

With team members scattered across Prague, Brno, and beyond borders, building bonds ain't easy, but we're not ones to back down from a challenge. That's why we came up with Backend Onsite Day. Originally a monthly affair, we scaled it back to every two months to make it work for everyone. It's a chance to catch up, brainstorm, and maybe even grab a beer together.

Sharing Know-How Like a Boss

We take knowledge sharing seriously. Our weekly BE meetings aren't just about updates and project briefs - they are also our chance to pick each other's brains. Plus, we've got knowledge base packed with tech insights and project learnings. It's like having a cheat sheet for all things backend.

Reflect, Refine, Repeat

We're all about improvement. That's why we love our team retrospectives. Just recently, at the start of 2024, we huddled up for about an hour to chat about how things were going. Turns out, everyone is pretty happy being part of the team, which is great to hear - but we also came up with some ideas to make things even better next time. It's all about celebrating wins and figuring out how we can crush it even more in the future.

Growing Together

Personal growth is big on our agenda. Regular performance reviews and one-on-one chats keep us on track. And with internal training programs, education budgets, and buddy systems in place, we're all set to level up together.

‍

At the end of the day, it all comes down to communication. Whether it's a quick Slack chat or a face-to-face meeting, keeping the lines of communication open is what keeps our team humming.

So there you have it—our backend team's recipe for success. With a healthy dose of teamwork, communication, and a sprinkle of resilience, there's no limit to what we can achieve together at Cleevio.

all posts