Bitrise Reviews

Our primary use case for Bitrise is that we adopted it as our end-to-end mobile CI/CD platform for both iOS and Android applications. As an SRE, I was tasked to migrate the mobile build pipelines away from the fragile Jenkins setup. Bitrise now handles automated unit and UI testing, code signing, artifact packaging, and the deployment to Firebase distributions for internal testing. We used to run about 80 to 100 pipelines, around 80 to 100 builds per day, and those were across different Git repositories. We consolidated it into a single application, which was Bitrise.

The best features which I appreciated about Bitrise was the easy drag-and-drop of pipeline editors. Even a non-technical person could understand it. Bitrise handles the headache of iOS signing, code signing, and certificate provisioning profiles automatically.

Bitrise also catches flaky tests over time so we know which tests are reliable and which are unreliable. The code signing automation of Bitrise has saved a lot of our time. Earlier, things which used to take weeks, now have reduced to days.

The impact of Bitrise in our organization is that prior to Bitrise, mobile releases happened every two weeks or were frequently delayed by build environment issues, code signing feature failures, or manual steps that fell through the cracks. Within three months of going live on Bitrise, we moved to weekly releases, and now we have a reliable hotfix pipeline that can ship a production build within 45 minutes to an hour of a fix being merged. For me especially, the reduction of pipeline-related incidents has been the biggest win.

We used to see two to three system build failures per week earlier, and after implementing Bitrise, the number went close to zero. The reproducibility of a clean build environment has eliminated that entire category of failures.

The improvement I would suggest for Bitrise is that the cost is significantly the friction point. Mac build machines are considerably more expensive than Linux equivalents. As our team has grown, the monthly bills have scaled accordingly with limited room to optimize without reducing concurrency. The self-hosted runner option was evaluated as a potential cost-saving measure, but the documentation and tooling for it are still less mature than the cloud product.

Build debugging remains a log parsing exercise. There is no interactive debugging session or live SSH access into a failing build environment, which would be a meaningful productive improvement. The analytics dashboard is very minimal and basic and lacks the depth that anyone would want for capacity planning and trend analysis.

I have been using Bitrise for around a year and a half.

Bitrise is pretty much stable.

Bitrise's scalability is strong. The cloud infrastructure has been highly scalable across two years of heavy use. We have experienced fewer than five incidents or four incidents of elevated queue times. In each case, Bitrise communicated proactively through their status page. Scaling to accommodate a new app or higher build concurrency has required zero infrastructure work on our part. The platform abstracts all capacity management, which aligns well with our team's approach. The only scalability challenge is economic rather than technical. Adding capacity comes with a proportional increase in cost, with no volume discount available to us on the enterprise plan.

The customer support and services on the enterprise plan are solid. The response times are fast, and the support engineers demonstrate genuine technical depth. They understand mobile build toolchain, code signing internals, and CI/CD architecture, not just the Bitrise product surface. We had two urgent support incidents during release-critical build failures, and both were resolved within an hour or two with clear communication throughout. The documentation is comprehensive for standard use cases. The community, such as Slack and the GitHub issue thread for individual steps, are also useful supplementary resources for dealing with edge cases.

Earlier, we used to do it manually with our team. We didn't have any platform for this, and then we got introduced to Bitrise. It helped us tremendously.

The migration process from Jenkins to Bitrise was smooth. I obtained documents online and it was straightforward.

We used AWS as our cloud provider.

We did see a return on investment with Bitrise. It saved a lot of time for us, and in the tech business, time saved is equally proportional to money saved.

My experience with Bitrise pricing, setup cost, and licensing was good. The pricing point was a pinch point for us, but the rest was good. We didn't face any challenges. The overall experience was positive for us.

For those who have the use case of reducing the timeline and getting automated builds, Bitrise would be a very good investment.

Bitrise reduced our pain point, which was the release process. Earlier, we used to have a two to three week gap, and then we would still face further delays. After Bitrise, that was resolved, and a huge time saving was realized for us. The overall review rating I would give to Bitrise is an 8 out of 10.

My main use case for Bitrise is as a build and deployment mechanism. I use Bitrise at the end of the day to generate a nightly build and also for all our release processes to the App Store and Play Store. It helped us with our main use case by solving issues around parallelization in the generation of the builds and also how to generate a build per pull request and share the artifact with the developers without giving them access to Bitrise itself.

Bitrise positively impacted my organization because the company used to do a release monthly or every two months, but with Bitrise system, we were able to optimize the process and now we do bi-weekly releases.

In achieving bi-weekly releases with Bitrise, we noticed improvements in time saved. Our release and build process went really fast, taking 20 minutes to generate a build for developers to test and for QA, and that is all thanks to Bitrise for always bringing the latest machines, having their system updated, and maintaining it well.

I believe the best features Bitrise offers include their support team, which is the best feature they actually offer. They are really helpful and always jump in to help and are genuinely interested in your process and how to optimize your internal deployments and building system. Recently, they gave a new scaffolding to make the boilerplate easier and to structure your Bitrise files, so that would be the best feature they have right now.

Bitrise gives you full control on the virtual machine and the processes, which has helped me specifically. They encourage you to do things right but don't force you to go through a template or a specific recipe that they have, so you can actually write your own scripts. Recently, for the EPO launch, we were coordinating the integration with Warsquare, a third-party company, and Bitrise actually helped us to do the connection between the virtual machine and their services, even though they are not required to do that. Whenever we spot any bug around our building process, they always jump in to help with a custom script, feedback, or insights from other clients that they have, and they also investigate for themselves what the problem was.

Bitrise's support team always receives feedback, so if you have any blocking point or improvement area, you can share it and they actually do it, which is something that surprised me. What they can improve right now is around the charts and metrics they provide. Right now, it is pretty generic about the performance of your machine and how much time each process takes, but they could evolve those charts to be more mobile DevOps metrics specific.

I have been using Bitrise for the last five years.

Bitrise is stable, pretty much.

On a factor of a Bitrise client, I think its scalability is great. They allow you to launch as many machines as you can.

Bitrise's customer support is really good. They are quite supportive and always answer. The only thing that might be an impact if you are an American company is that most of their team is based in Europe, so for critical feedback or bug resolution that requires an architect from their side, you might need to wait until the next day or use European hours, but they always have someone on call.

I did not previously use a different solution before Bitrise at Hinge Health, but I was using TestFairy and App Center before. I switched to Bitrise because it is more stable and it gives you full control of the virtual machines and is easier to implement.

Around time saved, I think is where we got the best return on investment with Bitrise because our build process went from taking hours to 20 minutes or even faster. Regarding other money saved or employees needed, I do not have any specifics around that.

My experience with the pricing, setup cost, and licensing with Bitrise was positive. They have a credit system and then evolved to a build number system. They also give you a buffer. For example, if you are reaching your limit, they notify you, and you also have a buffer. They guarantee you that you never run out of processes, ensuring that you will always be able to generate your build, no matter if you expand or pass that limit, and then coordinate in your next schedule an expansion of the number of builds or credits that you can use.

Before choosing Bitrise, I evaluated other options including TestFairy and Runway, but at the end of the day, we stuck with Bitrise because it was what was already implemented at Hinge Health.

I advise others looking into using Bitrise to make sure that you have a good understanding of user roles and to whom you provide access to the tool, and to have a clear understanding of mobile operations. Whenever you use Bitrise, feel free to reach out to customer support for integration and help, because they can schedule one-on-ones with their experts and provide you with a full onboarding on how to use Bitrise and do things properly. I would rate this experience a 10 out of 10.

My main use case for Bitrise is the deployment of our application to the iOS store and Android store, mainly.

We migrated our pipelines from Bitrise to GitHub because we wanted to unify our tools. A simple example is our application deployment, where we automated all the processes from building to deployment and testing within Bitrise.

Another use case that we had for Bitrise was the automatic building of the application and automatically depositing it to a bucket in which our QA team retrieves all the information, not just about the building but also the artifact, so they can do automated testing in other platforms.

The best feature Bitrise offers is the friendly UI that allows you to configure your own pipeline by dragging and dropping everything.

Specifically, the drag-and-drop UI and custom code steps have helped us because at some point, we had two applications, one for businesses and one for people in general. The UI allowed us to duplicate the workflow, so we did not have to configure it again, just changing some specific variables.

Bitrise has positively impacted our organization by providing a huge improvement at the very beginning of our operations. We previously used Azure Pipelines to deploy our application, which took two to three hours for an iOS deployment, while Bitrise reduced the simple building time to just 45 minutes.

The faster deployment with Bitrise allows us to get to the market quickly, enabling us to receive feedback from clients rapidly, test our application internally, and deliver more robust solutions efficiently.

Bitrise can be improved by perhaps showing the statistics of usage without requiring a greater subscription, as the prices were really high compared to other tools and we lacked metrics of our usage, such as how many builds were completed and how many failed.

Bitrise did what it needed to do during my time working with it, and I do not think anything else was needed since it was really easy to use, and its runners were really fast and optimized to do their job well.

Regarding Bitrise's AI capabilities, I do not know much about its governance and security, as when I was working with them, the only AI features I used were a chatbot, which did not provide much information about how they manage the information.

As for Bitrise's AI capabilities, the accuracy and reliability of output were not that good. Most of the time, it redirected me to a human or advised me to open a ticket, so it was not really useful.

I have been working as a DevOps engineer for three years.

Bitrise was stable.

We did not have the chance to make really huge solutions or pipelines. I think Bitrise has worked a lot on scalability, and I find it really scalable because you can create small portions of code or stages that can be reused in other workflows.

My experience with customer support at Bitrise was really nice, as they were very patient, particularly with my non-native English speaking. They were always checking if we needed something, which was really good.

It was really amazing to work with Bitrise. They have a really good customer support team, and technically, everything was really good. They found an employee who speaks Spanish to join one of our meetings, making it easy to continue our negotiations.

We previously used Azure Pipelines and switched to Bitrise because it was way faster, had many integrations, and was really easy to set up. The UI helped us a lot to do our job well.

I have seen a return on investment with Bitrise, as at the very beginning, our deployment times for our iOS application were three hours, but with Bitrise, it was reduced to just 45 minutes, showing it was really fast.

My experience with pricing, setup cost, and licensing for Bitrise was positive since it was really cost-optimized. The setup cost was actually null, and it was really easy to set up and renovate the licensing.

We evaluated CircleCI and GitHub Actions before choosing Bitrise.

My advice for others looking into using Bitrise is that it is a platform to start new products, giving you an optimized version of a runner with good customer support that you can reach out to for anything you need. I would advise choosing it with complete confidence. I would rate this review a 9.

Currently, we are building and deploying iOS and Android applications through Bitrise. We have a web maker tool through which we build the iOS IPA and Android APK packets. We have multiple pipelines over Bitrise, and in a single project, I have multiple workflows in which one workflow deploys the application over bitrise.io and one pipeline I use to deploy over the Play Store and App Store. The main use case is building the Android packets and iOS packets and deploying them over the Play Store and App Stores.

The best features I would say are that if we want to build an application for iOS, we would normally need a Mac, but with Bitrise, we do not need any Mac as Bitrise already provides virtual machines based on my requirements like which Xcode version I have to use, what Android SDK versions I need, and what Java version I need. Everything Bitrise gives me on its VM machine.

The way Bitrise provides the connectors is a good thing. The main thing which I love about it is that you do not have to write a full script and coding. It is not required in Bitrise as it gives a lot of plugins and we use fastlane, so Bitrise also gives us the flexibility to use fastlane to write the automations. That is also a good thing.

Previously, we used to have multiple MacBooks through which we manually requested a person to deploy the build the application and share the IPA link and APK link with us. But now we have automated everything through Bitrise as it gives on-demand virtual machines and Macs. This is a big benefit, and we have reduced the DevOps engineer count from five to three to manage the mobile applications.

The biggest improvement I would say is that in the workflow, we have a plugin script, and that script window is dynamic. If we are writing something, it automatically gets shrunk. This is the biggest flaw which I have seen in Bitrise. If I am writing any script, it gets shrunk dynamically, and that should be removed or we should be given an option to disable it.

The second thing is that currently we are using Harness to deploy our applications. Other platforms like Jenkins have set up webhooks through which we do not have to manually deploy any application and trigger the jobs into Harness. I want the same thing with Bitrise; we should get a Harness connector over Bitrise so that through Harness, we can trigger Bitrise workflows, and we should not give access to all the dev and QA for triggering the workflows. I would suggest that if we can have one Harness connector through which developers just trigger the build and automatically a job gets triggered to Bitrise.

I have been using Bitrise for three years.

Bitrise is stable.

As our code size is increasing, I have never faced challenges scaling my builds as Bitrise gives us the flexibility to increase the virtual machines. Bitrise's scalability is also good.

I have communicated multiple times with Bitrise support regarding my builds and in case we want any older machines. The customer experience I have had is very good. They are very responsive.

Previously in my old setup, we had fastlane through which we used to manually deploy the applications over the TestFlights and Android beta releases. That was everything manual, and here we save a lot of time because I have set up the job triggers through which if anyone is committing to the branch, automatically Bitrise starts building the app, and if it is a development environment, it uploads to bitrise.io. I have also integrated the Microsoft plugins through which automatically developers and QA get notified, and they can download the applications from bitrise.io. Once the testing is done, we manually trigger the job workflow over Bitrise, and it deploys the applications over the TestFlights and beta releases.

The first time I have used Bitrise.

Previously, we used to take one day to deploy the application, but now in thirteen to twenty minutes through our automation and with the help of Bitrise's flexibilities, we deploy the application. That is where we save a big amount of time.

Bitrise supports RBAC, which is the main point where we can isolate our projects based on the developers, QA, and all. We can isolate the accesses and authorization. That is a big point.

I cannot comment much on the governance side because we have never faced any security issues whenever we had an audit. It also provides us the feature of secrets where we can encrypt the secrets, and I think from the perspective of governance and security, it is a good one.

Previously, we had five DevOps engineers, and now we need three DevOps engineers to manage Bitrise. Previously, we had to be dependent on MacBooks, but here we are not dependent on MacBooks as on demand we get the virtual machines and we perform our tasks. I think we have saved a lot of cost.

On the licensing side, we do not manage that, as we have a different team that manages that. The costing is much less if we compare it to acquiring different MacBooks and building the applications. It is cheaper for us.

I did not evaluate other options before choosing Bitrise.

If any organization is having a mobile application, I would recommend them to use Bitrise because of its flexibility, scalability, and cheap and on-demand prices. I have rated this review nine out of ten.

My main use case for Bitrise is for CI/CD, which means generating the build, deploying the build into the Play Store and App Store.

I am from the mobile field, and we were generating manual builds, which took more time, so we selected Bitrise. We wrote scripts over Bitrise, set up our application, and generated the application using the AAB and APK formats.

In the product that I am working on, I share two frequent builds to the QA, product team, and management, so I generate multiple builds—seven to eight builds in a day, which sometimes takes more than an hour or two hours. By using Bitrise, my two hours of daily effort was reduced. I simply go to Bitrise and generate the build, so there is no manual effort required for me to generate the build.

I use GitHub Actions as well, but Bitrise has an option to upload multiple keystores. I uploaded the keystore and generated some values including the keystore name, keystore password, alias, and keystore name. I mapped those keys to the global variables in Bitrise, assigning these keystore values to particular variables and picking the keystore based on my script. If I am working on product X, I pick this keystore; if I have product Y, I pick a different keystore.

I am using Bitrise totally for CI/CD, generating the build and deploying the build into the Play Store.

One of the best features is setting up multiple applications. The best feature is that we have a single code for multiple applications and multiple keystores for generating multiple applications and multiple APKs. Bitrise has the support to use multiple keystores, by which we can generate multiple unique applications and deploy them directly to the Play Store.

Bitrise is positively impacting our organization by saving manual effort—saving two hours of every developer effort. In Android, it saves two hours, but in iOS, when we are generating the iOS build, it takes more than an hour. With Bitrise, as a team of 10 to 12 people, we are able to independently generate the build and save overall 20 to 40 hours per day.

If a developer saves two hours of time, he can spend these two hours on any particular feature or any CRS completion. We just need to go to Bitrise and generate the build, and the build will create in parallel while I can complete my work on my local system.

Bitrise has to work more on the error part. Sometimes I face issues when I trigger a build to generate, and I get a build failed without getting the proper log, which sometimes makes the user too annoyed. In local, it works fine, but in Bitrise, I am facing issues. We should not get any option that requires updating the workflow or anything. This is something Bitrise has to improve.

I have been using Bitrise for the last three years.

Bitrise is stable.

Scalability is great. Whenever I am doing anything, I have not felt any glitch; it is working as expected.

Customer support for Bitrise is awesome; they are responding very quickly. Sometimes I face issues in Bitrise, so I reach out to the support team, and they reply within a given timeframe, so I am happy with the customer support as well. They are very quick. I would rate the customer support a 10 out of 10.

Positive

Before Bitrise, I set up Jenkins for research and development purposes; my company set up Jenkins, and I have tried GitHub Actions as well.

I chose Bitrise because it is extremely easy and simple to integrate, and you can set it up with Bitbucket.

If I am saving my developer efforts, it is helping my team to focus on other parts, which helps me and my team to deliver more features. If we deliver more features, it will ultimately generate revenue for my company.

For the pricing part, I discussed with my manager, who was happy, so I am also happy. He is able to get the approval every year, and we have an active subscription right now, so it is good for us, and I am okay with the licensing and setup cost.

I choose a rating of 8 out of 10 for Bitrise because it is fulfilling almost all my needs regarding deploying the build into the Play Store, managing multiple applications, and doing everything. I am keeping two points off just because of error handling; whenever we are getting an error, we do not have much clarity on the error side.

We are using Bitrise, specifically bitrise.com, and we are doing some scripting and setting up in my local. We have integrated our Bitbucket with Bitrise.

I recommend others to use Bitrise; it will save your time for generating manual effort and deploying the build into the Play Store, making that part easier without any manual effort to generate the application, deploy it into the Play Store, and handle tasks like that.

My primary use case for Bitrise is automating CI/CD pipelines for mobile application development, including build automation, testing, code signing, and release management for Android applications.

A recent example of how we use Bitrise in our workflow involved automating the release pipeline for a banking mobile application, where we configured Bitrise to trigger builds automatically on pull requests and releases, run automated tests, manage code signing, and deploy successful builds to staging and production, significantly reducing manual effort and improving release consistency.

The best features Bitrise offers are a mobile-first CI/CD platform, easy workflow automation, Android build support, and automated testing.

The automated build and deployment workflows in Bitrise have made the biggest difference in our organization, greatly reducing manual release overhead and improving our deployment speed.

Bitrise is useful for teams managing complex mobile release workflows because it simplifies the automation and reduces the operational friction.

Bitrise has positively impacted our organization by accelerating release cycles, improving CI/CD reliability, and reducing manual intervention, which has improved overall development efficiency.

It reduced the release time by approximately 50 to 60 percent, improved deployment consistency, and also reduced our manual intervention in mobile releases.

Bitrise can be improved by offering a more customizable dashboard, faster troubleshooting for failed builds, and more advanced cost visibility for pipeline usage.

The core CI/CD capabilities of Bitrise are strong, but most improvements would be around analytics, visibility, and workflow optimization.

Bitrise is a very good platform with strong CI/CD capabilities, but the platform needs to improve its analytics and reporting, faster troubleshooting for failed builds, and also more advanced cost visibility in pipeline usage.

More detailed cost optimization insight and advanced pipeline performance recommendations would be more useful for Bitrise.

I have been using Bitrise for about six to seven months.

Bitrise is stable and dependable for daily CI/CD workflows.

Bitrise's scalability is very good; it scales well as our project complexity and build volume increase.

Customer support from Bitrise has been responsive and helpful.

Previously, we used a combination of manual scripts and general-purpose CI/CD tools for our mobile app delivery before switching to Bitrise.

The setup for Bitrise was relatively straightforward, and the pricing is reasonable considering the automation and time-saving it delivers for mobile development teams.

The ROI from Bitrise comes from a faster release cycle that also reduced our manual deployment effort and improved our developers' productivity.

We evaluated Jenkins, GitHub Actions, and CodeMagic before choosing Bitrise.

If your team works heavily on mobile apps, Bitrise is worth considering because it simplifies CI/CD significantly; investing time in designing efficient workflows early is advisable.

Bitrise is a strong platform for mobile CI/CD automation, helping reduce release complexity, improve delivery speed, and enabling the team to ship mobile applications more efficiently.

I would rate this platform an 8 out of 10.

Bitrise is used primarily to automate CI/CD pipelines for mobile application development, including build automation, testing, code signing, and release management for Android and iOS applications.

Bitrise is used daily to manage build pipelines, monitor deployment workflows, troubleshoot failed builds, and streamline the mobile release process.

A recent example of how Bitrise has been used in the workflow involved automating the release pipeline for a mobile banking application where Bitrise was configured to trigger builds automatically on pull request and release, run automated tests, manage code signing, and deploy successful builds to staging and production, significantly reducing manual efforts and improving release consistency.

Bitrise has positively impacted the organization by accelerating release cycles, improving CI/CD reliability, reducing manual intervention, and improving overall development efficiency.

Release time has been reduced by approximately 50% to 60%, achieving faster builds and test cycles, improved deployment consistency, and reduced manual intervention in mobile releases.

The best features Bitrise offers are a mobile-first CI/CD platform, easy workflow automation, iOS and Android build support, code signing management, automated testing, deployment integrations, and a strong developer experience.

Automated build and deployment workflows in Bitrise have made the biggest difference, greatly reducing manual release overhead and improving deployment speed.

Bitrise is especially useful for teams managing complex mobile release workflows because it simplifies automation and reduces operational friction.

Improvements I would like to see in Bitrise include more customizable dashboards, better analytics and reporting, faster troubleshooting of failed builds, and more advanced cost visibility for pipeline usage.

The core CI/CD capabilities of Bitrise are strong, and most improvements would be around analytics, visibility, and workflow optimization.

Bitrise has been used for around one year.

Bitrise has been found to be stable and dependable for daily CI/CD workflows.

The accuracy and reliability of output from Bitrise are impressive, as the platform is reliable and performs well for build and deployment automation, with minimal downtime or major issues in this experience.

Bitrise's scalability is very good, as it scales well as project complexity and build volume increase.

Customer support from Bitrise has been responsive and helpful.

Previously, a combination of manual scripts and general-purpose CI/CD tools were used for mobile app delivery before switching to Bitrise.

The experience with pricing, setup cost, and licensing was that setup was relatively straightforward, and pricing felt reasonable considering the automation and time saving Bitrise delivers for mobile development teams.

Bitrise was not purchased through the AWS Marketplace; instead, it was purchased directly from the vendor.

A return on investment has been seen from Bitrise, which comes from faster release cycles, reduced manual deployment effort, improved developer productivity, and better release consistency.

The experience with pricing, setup cost, and licensing was that setup was relatively straightforward, and pricing felt reasonable considering the automation and time saving Bitrise delivers for mobile development teams.

Before choosing Bitrise, options such as Jenkins, GitHub Actions, CircleCI, and Codemagic were evaluated.

I would advise others looking into using Bitrise that if a team works heavily on mobile apps, it is worth considering because Bitrise simplifies CI/CD significantly, and I recommend investing time in designing efficient workflows early.

Bitrise is a strong platform for mobile CI/CD automation that helps reduce release complexity, improve delivery speed, and enables teams to ship mobile applications more effectively and efficiently. This review has been given a rating of 8.

My primary use case for Bitrise is for continuous integration and continuous delivery, commonly known as CI/CD purposes. I use Bitrise to automate repetitive tasks of managing my app's life cycle for sharing multiple builds with the QA team, product team, and for finally releasing the build to the App Store or Play Store.

Being in the mobile development field, I have to constantly handle multiple apps for my organizations. I need to share these builds across QA teams for both iOS and Android and with product teams for their reviews and for their tasks. Doing so manually would take a lot of time, but if I automate this process using Bitrise, I can easily share and easily reduce this time-consuming task.

Primarily in case of iOS development, the build-making process is quite complex due to provisioning profile handling and related tasks. Bitrise simplifies that process completely for me.

The best features Bitrise offers include direct deployment to the App Store and Play Store and direct connection to both TestFlight and App Store releases, which is a great Bitrise tool.

Doing the task of direct deployment manually can lead to several bugs in the release pipeline process, but once I automate it using Bitrise, this particular task is taken off the developer's hand and is automated, saving a lot of development time.

The integration is quite simple, and once done, I do not need to revisit it again. Bitrise can easily handle multiple applications.

Since I started using Bitrise, the development time, specifically the time that I spend on sharing these builds and handling the release process, is significantly reduced.

A ballpark figure indicates that I save around three to four hours per week since using Bitrise.

Sometimes the builds fail, and the error messages that I get are not very descriptive. That could be improved.

I give Bitrise an eight out of ten because sometimes builds fail, and the error paths are not that descriptive.

I have been working in my current field for more than twelve years.

Bitrise is stable, apart from the odd build failure.

Apart from the odd build failure, Bitrise is quite reliable in its accuracy and reliability of output.

Bitrise's scalability is quite good. I have automated multiple apps from the same organization across iOS and Android, and they work quite well.

The customer support for Bitrise is good. I never faced any issues.

I previously tried Jenkins. Different organizations prefer different tools, so in my previous organization, I used Bitrise, while Jenkins is also used in my current organization.

The integration is quite simple, and once done, I do not need to revisit it again.

I have evaluated Jenkins before choosing Bitrise; it is also a good tool.

My developer's time is definitely saved, and I can say that in a week, three to four hours are easily saved.

I would advise others looking into using Bitrise to definitely try it, as they can save a lot of their developer's time. The automation part, the redundant part of sharing builds and managing app lifecycle can be handed over to an automated system, significantly improving their output.

I rate this product an eight out of ten.

My main use case for Bitrise is to generate builds for iOS and Android applications using Slack commands to directly trigger the builds from Slack to Bitrise and also create a CI/CD pipeline.

A quick specific example of how I use Bitrise in my daily workflow is that when a developer provides us with a branch to generate a build, we use a Slack command to trigger the build on Bitrise. Then Bitrise generates the build. In the Bitrise workflow, we have added AWS plugins. Bitrise sends the build to AWS, and then the automation is run on AWS Device Farm using the automation code which is available on GitHub.

I also use the Bitrise public URL for sharing the builds with the team.

The best feature Bitrise offers is the user-friendliness. Without interacting with the YAML file, I can directly use the user interface to add different types of plugins. Bitrise also provides Slack webhooks directly, allowing me to use Slack commands to trigger the builds directly on Bitrise.

The user interface makes things easier for me because I do not have to log in repeatedly in Bitrise to generate the builds. I just use the Slack integration and Slack commands to trigger the build on Bitrise and then use the public URL to download the build directly on our testing devices.

Bitrise has positively impacted my organization because previously we used to generate builds on our local machine, which was very time-consuming. Now all the build generation and the automation execution are directly done on Bitrise, and the automation execution is triggered from Bitrise to AWS Device Farm.

Bitrise can be improved because it has limited debugging capabilities. If there is an error in build generation, it is somewhat difficult to debug what exactly the error is.

I would also mention that there is a learning curve when using Bitrise, and it would be useful if the documentation were more detailed.

I have been using Bitrise for the last two years.

Bitrise is very stable. I have observed downtime very rarely, only one to two times in the last two years.

Bitrise's scalability is good. Before we used to have small applications, around 50-60 MB, and now we have application sizes from 300 to 400 MB without facing any issues when generating larger builds for IPA files and APK files.

I actually have not needed to interact with customer support because I have found solutions directly online.

Before Bitrise, I used GitHub Actions but found it was not as user-friendly. We needed to add workflows manually in the YAML file, whereas Bitrise gives us the user-friendliness to add different plugins in our workflow.

I have seen a return on investment. The time saved is significant since the resources used by our local machine are not required when using Bitrise build generation.

My experience with pricing, setup cost, and licensing has been that previously we used to use a small organization plan, which we did because Bitrise is somewhat pricier.

I did not evaluate other options before choosing Bitrise. I directly switched from GitHub Actions.

I would suggest others looking into using Bitrise to use it because it is very user-friendly and has integration with different services such as AWS Device Farm, Slack incoming and outgoing webhooks, and can be used for the CI/CD pipeline.

I think Bitrise is a really good cloud generation portal where users can easily onboard their Android and iOS applications and generate builds without using local resources.

I rated Bitrise a nine on a scale of one to ten.

I chose nine for my rating because it is really easy to create a CI/CD pipeline directly on Bitrise. First, the build gets generated on Bitrise cloud services. Using the workflow, we can add the AWS Device Farm workflow, and the build directly gets shared with AWS Device Farm along with the code and automation code which is available on GitHub. Once the automation is completed, the automation results are directly shared on the Slack channel.

Regarding Bitrise's security capabilities, I think its governance and security are secure since the builds generated are not shared with everyone. We can choose if we want a private or public URL. Thus, if we choose private builds, then the builds are not shared with anyone. Also, when generating a build, Bitrise takes the pull request from our GitHub repo, which is done in a secure manner.

In terms of Bitrise's AI capabilities, I find its accuracy and reliability of output to be really accurate because it has accelerated debugging. The AI analyzes the failed build logs and also summarizes this on its build page. Sometimes, the AI does the build fixing correctly and also applies changes to create a pull request for our repository.

For our mobile application development, we have integrated Bitrise with our Git repository, mainly GitHub. Whenever the code is pushed or pulled, the pipelines get triggered and then connected to the mobile development tools. Bitrise builds the environment and compiles the application. We integrated the notification tool to receive build updates. Bitrise can also integrate with the internal testing tools, which is very beneficial for us. Bitrise gives us the full development life cycle automation, and it is very good to use.

Every mobile application development needs automation for building and testing and then deploying. Bitrise has given us a perfect platform which is needed for the automation in mobile applications. The teams which are building iOS and Android applications with frequent updates can benefit significantly. For some updates, we can do manual things, but for frequent updates, Bitrise is very useful and suitable for the teams. It gives faster feedback on code changes, making it good for frequent changes.

Bitrise offers pre-configured workflow steps, which are designed specifically for mobile applications. Because of these pre-defined workflow steps, it simplifies tasks like building iOS and Android apps, running test cases, and generating artifacts. These pre-defined workflow steps have helped our team because when our code is pushed to GitHub and creates a request, it simplifies the tasks like building iOS and Android apps, running test cases, and generating artifacts.

Bitrise has impacted our organization positively because the experience was very smooth. The platform has provided a clean dashboard so that our team can monitor the build and the pipeline execution, including what the status of that pipeline and build are. Bitrise workflow settings are relatively simple because of the CI/CD templates which it offers for mobile applications. The documentation was also very useful for advanced pipelines, making it a reliable platform for managing mobile build automation.

One improvement Bitrise can have is enhanced debugging tools for analyzing failed builds. If any build gets failed and there is availability of a debugging tool, then it will become easy for us to debug that build problem.

I chose nine out of ten because the improvement that a debugging tool for analyzing the failed build is important. If it is present, then it would become easy for us to debug and it would become a perfect ten.

I have been using the solution for the past six months.

The process I have described covers how we have integrated Bitrise in our mobile application automation. My overall rating for this product is nine out of ten.