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 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.

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 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.

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.

My main use case for Bitrise is to build and deploy mobile apps. To build and deploy my mobile apps using Bitrise, I clone the code repository with Git, realize the build of the mobile application, apply tests, SAST and DAST verification, and publish this app on the stores, Apple or Google.

I think the best feature of Bitrise is the flexibility to use third-party engines like Fastlane.

I use third-party integrations like Fastlane with Bitrise to avoid vendor lock-in, facilitate my migration to another platform, and have a unique workflow for deploying about twenty to thirty apps.

Bitrise has had a significant positive impact on my organization because we do not have any other platform to realize these builds and deploys with mobile apps.

Bitrise has helped reduce errors in my workflows because I have tests, E2E tests, integration tests, and Appdome tests.

Bitrise has a strong mobile focus, and what could improve is the native support for reusable pipeline modules like actions in a GitHub Action, better templates, think Terraform style but for CI, and easier parameterization across workflows.

Templates would be a significant improvement for me. It is the one thing I need and it would make my life easier with the workflows.

I have been using Bitrise for four years.

Bitrise is sometimes stable, and sometimes I experience problems with Bitrise.

Bitrise's scalability is adequate.

Bitrise customer support is slow but functional.

I am not using a solution different from Bitrise. I am working on a migration from Bitrise to GitHub Actions because the cost is lower.

Before choosing Bitrise, I did not evaluate other options.

You should consider Bitrise as it is a strong platform when used appropriately. The biggest mistake is treating it like a general-purpose DevOps solution. I would advise others that Bitrise is best used for its intended mobile focus, and this approach saves you time. I would rate this product a seven out of ten.

My main use case for Bitrise is for iPhone CI/CD and App Store Connect build deployment.

I am using Bitrise for iPhone CI/CD and App Store Connect to take a Git clone, create a build, deploy to the App Store, and send a push notification to the teams that the build is uploaded and it is in review.

I am using the Xcode build, which is really working great for me in Bitrise.

The best feature of Bitrise is that it gives a drag and drop interface, so you don't need to code in the YAML, making it very easy compared to other platforms.

The drag-and-drop feature helps my workflow because I just have to select which tool I want to use. For example, if I want to add the test cases, I can search for test cases, and if that is available, I can directly drag and drop it in my current workflow above or below a specific other task, and then I just have to add the input parameters. In contrast, with a YAML file, I have to add all the data and read the documentation, but with drag and drop, it is easy.

Bitrise has positively impacted my organization by helping me reduce time by around 50% or more while I am using it for my personal project.

Bitrise saves me time mainly in building, testing, and deployment because I don't have to use my own machine to check the data or change the branch for that.

Currently, I haven't found any features in Bitrise that can be improved, but related to Xcode, they need some extra tools that are available in the market, or they have to give specific errors, which are currently hard to find when there is so much log.

They need to add some extra documentation for how to use the parameters, such as variables, where to add them, and how to use them below the workflow.

I have been using Bitrise for around five years.

Bitrise is very stable in my experience.

Bitrise's scalability is fine for my needs as of now, and I see no need to change anything.

I have used the community support for Bitrise, and it is great. I haven't reached out to customer support.

Bitrise is the first one I have used, and I haven't used any other solutions.

I can see a return on investment with Bitrise, but since I am using the free tier, I don't have any idea about the pricing and those things.

My experience with pricing, setup cost, and licensing for Bitrise would be good, but I haven't used that because I am using the free tier.

Before choosing Bitrise, I haven't evaluated other options.

I chose eight out of 10 because currently, it is easy for me, but there is some documentation missing, and also related to iOS development, there are some use cases that are not in the support portal, so I have to find it out by myself. On a scale of 1 to 10, I would rate Bitrise an eight.

My main use case for Bitrise is to generate QA of our mobile app so our team can test it. A typical day for me includes working on a feature, doing the tasks I have to do, and when I finish, I generate the QA with Bitrise and send it to the testers.

The best features Bitrise offers, in my opinion, are the QA itself, the artifact it generates, and the log, which makes it very simple to know what step we got an error or the log for the error, so we know what we have to do to fix it.

The logs help us significantly; for example, if we generate a QA for Android and iOS, and if a specific step for Android fails, I can look at the log and see exactly what step we got an error, and with this log, we can find out what went wrong.

Bitrise has positively impacted our organization by improving release speed.

I think Bitrise could be improved if it was easier to generate Android QA and iOS at the same time.

I have been working in my current field for about five years.

I think Bitrise is stable, and I do not remember having any problem with stability.

I think Bitrise's scalability is very good.

Bitrise was the first and only solution we used; I did not previously use a different solution before Bitrise.

I would advise others looking into using Bitrise to start using it; it is a very good tool. There is no other relationship between my company and this vendor other than being a customer. I give Bitrise an overall rating of 8.

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.