Bitrise Reviews

My main use case for Bitrise revolves around its significant role in my day-to-day practices, as I use it for CI/CD pipelines in my Android and iOS applications, primarily for automatic build and testing, which helps catch issues early and speeds up the development process.

Bitrise helps me catch issues early by utilizing certain rules we have set using JSON, which are beneficial. For example, if there is any provisioning profile mismatch, the pipeline fails and does not run. This catches early that some parameters are not matching in the release, saving us a lot of time, and sometimes a production release has been automatically tested before it launched.

The only downside I have to mention about my main use case is that debugging a failed build can sometimes be time-consuming, and whenever the build fails, it becomes expensive for the larger projects. This happens rarely, but it does occur.

In my opinion, the best feature Bitrise offers is its workflow automation, which I have used to some extent, but it makes my build, test, signing, and distribution in Android and iOS apps easy whenever my code is pushed, saving a lot of time compared to the manual process that takes hours.

What I appreciate most about the workflow automation in Bitrise is its flexibility. Setup can be critical at times, but it is a one-time task, which is acceptable. Flexibility is key because I do not have to keep running my work in parallel with waiting for it to complete, as the pipeline saves a lot of time.

Bitrise has positively impacted my organization by providing us with a lot of flexibility and time-saving in terms of creating builds and sharing. It takes over processes that are no longer taking place on our system, allowing us to work simultaneously without waiting for Xcode to create a build, which is the main benefit.

I can share that after using Bitrise, we have seen a time savings of fifty percent.

I think Bitrise can be improved somewhat. For now, I do not have anything else to add about the needed improvements. I do not have any other improvements needed for Bitrise that I have not mentioned yet.

I have been using Bitrise for more than five years, working with Bitrise for pipelines and testing my mobile applications.

In my experience, Bitrise is stable.

We have evaluated Bitrise's scalability.

My experience with customer support for Bitrise was good, as we got our issue resolved in a fair time.

I would rate the customer support an eight on a scale of one to ten.

Previously, in one of my applications, the client preferred Jenkins, and when I searched for my company, Bitrise was the best solution I found online.

Before choosing Bitrise, we evaluated other options such as Jenkins and Fastlane.

I choose seven out of ten for Bitrise because it is making my life very much simpler, but the initial setup is somewhat complex at this time.

I have seen a return on investment as it is saving our time significantly, not in terms of money or anything else, but it is saving a lot of time.

My experience with pricing, setup cost, and licensing for Bitrise is that they are fair.

Regarding Bitrise's AI capabilities, I have not had more opportunities to explore that, as all I am currently using it for is providing builds and test cases.

I would not comment on Bitrise's AI capabilities regarding accuracy and reliability of output, as I have not used it much.

My advice for others looking into using Bitrise is to first clarify their need for CI and what exactly their requirement is. If they are looking for something for their mobile product, then I would definitely recommend Bitrise, but not for all types of applications, only for mobile applications.

I would rate my overall experience with Bitrise as a seven out of ten.

Public Cloud

Amazon Web Services (AWS)

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 automating CI/CD in the projects where I work. I use Bitrise to automate processes for pushing releases, building versions, and building PRs. When we open a PR, we automate the whole process, so Bitrise is responsible for running the project build, the unit tests that we have, and also checking that nothing is breaking in SwiftLint. These are the use cases that we have today in the company that uses Bitrise.

The best features that Bitrise offers are the automation and also the speed that we get. It makes easier some processes that we have internally here in the projects, adding speed, agility, and ease of maintenance of the project, and maintaining the quality of the code that we have in the project for the final delivery.

Bitrise helps speed up the development process in my team because we stop doing the whole process of pushing versions and build checks all manually. Bitrise does this in an automated way. We configure the tool and then it already does all this automatically and with agility in the process. It facilitates deployment processes for us here, reducing development time, configuration time, among other things.

A positive impact that Bitrise has had on my organization is that it kept the version releases consistent and we were able to catch PR problems, build and test problems, and SwiftLint issues during code review time. We were able to catch these points in an automated way through Bitrise. This had a very positive impact in terms of release deployment time and quality. Bitrise has helped us a lot in these processes. This has been a very positive impact for us here, especially because we work with several teams, and we don't have that much manual control over this. Bitrise manages to take care of this automatically and maintain the quality of the whole release process.

Today I don't see any improvement points for Bitrise. It serves us very well, and the project is going very well with Bitrise. At certain times we have failures within the tool itself where we need to debug, look at logs, and understand these points. Because of that, it wouldn't be a 10.

I have been using Bitrise for five years.

Bitrise has not had any stability issues for now.

I would rate Bitrise's scalability as great.

I consider Bitrise's customer support very good.

I have used Fastlane, but in some aspects the tool was not meeting our needs. So we migrated everything to Bitrise.

The interview was great and very intuitive. I was able to understand everything and the questions were very objective.

Bitrise was evaluated between Fastlane and Bitrise for continued use.

I would advise them to implement Bitrise as soon as possible in the project to make it easier to automate delivery and version release processes, including on the mobile side, which is my main area. I would give some suggestions for additional configurations. Bitrise with well-defined and well-configured processes is Bitrise that will work very well in an application. I would also advise them to understand which processes they need and what would be necessary within their project so that they don't make mistakes, so they can do an optimal configuration and have a great experience with the tool. I would rate this product a 9 overall.

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.

Public Cloud

Other

My main use case for Bitrise is that we use it as a CI/CD platform to build our Cordova applications and further distribute them to Apple and Google stores.

Regarding my main use case with Bitrise, the cases that we need to cover work great for us. We have an option to store distribution certificates and any other certificates that are required for the build to work, and the configuration is very straightforward.

The best features Bitrise offers include the option to cache builds, although we decided to stop using it because the builds don't take a lot of time. I think it's the simplicity of configuring the workflows and the simplicity of configuring parallel workflows. In general, there's an option to build native applications.

The simplicity of Bitrise impacts my day-to-day work and my team's workflow because we have a single YAML file stored as part of the repository that has been set in stone for quite some time. Whenever we need to introduce a new workflow that would be similar to an existing one but for a different customer, it's just copy and paste. We can also use the UI at the Bitrise website directly to select all of the steps and provide the values for the input fields. It's straightforward and there are not many steps needed to configure it and have it up and running.

Bitrise has positively impacted my organization since we need a way to build native apps for Android and iOS that is efficient and fast, so the delivery to Play Store and App Stores does not take hours. We are rather talking about minutes here, which means that we can react to any customer requests and deliver when there is a new feature or bug fix. We can quickly spin up the build and then have it available for external testers on Play Console or in App Store Connect.

What kept it from being a ten is because I don't give tens. It's a great tool and I think eight is a great number. There's always room for improvement and it's not the perfect tool.

Regarding Bitrise's AI capabilities, I think the accuracy and reliability of output are pretty accurate and reliable nowadays.

I have been using Bitrise for the past seven and a half years.

Bitrise is stable.

Scalability of Bitrise is great.

Customer support of Bitrise is great.

Before Bitrise, we use Bitrise and GitHub Actions in parallel. Bitrise is needed for our native builds to work.

My experience with pricing, setup cost, and licensing for Bitrise is that I cannot really say because I don't manage these things. I think it would be around 1,000 euros per month for around 18,000 credits or 12,000 credits, but I don't remember from the top of my head. The setup is easy and I think the price, considering what we need to use it for, is justified.

Private Cloud

Other

Deploying iOS and Android apps to the Play Store and App Store is the main use case for me with Bitrise.

I use Bitrise for deploying my React Native app, and for the iOS version, I have the setup for the yarn build and all my codebase script setup. I set that and all the configuration setup, including sign in with the App Store and all the configuration files, including a provision profile. I can get everything I need and start building. I also attach the pipeline with my GitHub, so whenever I push, the pipeline runs and uploads the new build with the increment version of the iOS build. For Android, I currently run differently because I need to run a different type of script for that.

Bitrise offers excellent pipeline-wise setup and all the setup scripts that are easy to use. The YML editor and all the tools are very useful, and that is the main purpose of Bitrise as a great tool to have.

The YML editor specifically helps me in my daily workflow by being a one-time setup with no hassle every time I need to check. It is a smooth process. The first time takes time to set up all the build-related pipeline setup, but as I use it further, it becomes quite smooth and easy to use. I can manage everything in one place, and I do not worry about any build errors. That is the main thing I can say.

Bitrise has positively impacted my organization because earlier we manually deployed, checked, and tested everything, which took much time to create a build along with machine-specific setups. After using Bitrise, it became very easy and hassle-free. It just becomes a matter of time to push the code, and everything runs smoothly. Deployment does not take much time. Bitrise is a very useful and time-saving tool, and it is very effective because we save our time and money in the organization.

Time-wise, before Bitrise, building an iOS build and an Android build differently while uploading took around four to five hours for me. Now with Bitrise, I do not need to worry about the build. I just push my code, and in the background, the Bitrise pipeline runs and uploads in less than thirty minutes. It is a very specific time-saving experience, and I also do not worry about creating a build, so I save considerable time regarding that.

Bitrise is quite usable, and the UI is good. There is no area for improvement I would suggest; it is perfect for me. Price-wise, I can tell that Bitrise could offer discounts.

Bitrise can be improved by adding some pre-setup builds already for iOS and Android setup with tutorials that are helpful to any new users. New users could see that they already have the pipeline created for platforms such as React Native, iOS, and Android without needing to create step-by-step setup. That is one improvement I can suggest.

I have been using Bitrise for the last two years. It is a very useful CI/CD tool for me, and I have been glad to work with Bitrise.

Bitrise is quite stable in my experience, with no issues, and it has been quite stable for me.

I do not need any customer support for my use case, and I have never used it because there is no need. Currently, there is no chance to have an error that needs customer support, so I have never experienced that.

Previously, we did not use any other tool before Bitrise. We heard about Bitrise and researched it, and planned to use it since it is a good tool that reduces hassle for build creation and helps us create our CI/CD setup.

Pricing-wise, Bitrise is at the higher end. We need some discounts if we are using it for more than a year or two years, and the overall pricing is also good. The setup cost and licensing are very good.

Before choosing Bitrise, we checked Fastlane and other tools, and we found Bitrise to be a financially appealing and easy-to-use tool, so we picked Bitrise for our accelerated development.

Bitrise is a very great tool.

For those looking into Bitrise for mobile-related development, if you are planning to create and upload a build for the Play Store, this is the tool I can recommend. I already shared Bitrise with some of my friends and others, saying it is very useful to reduce time and money. I rate this product a 3 out of 5 based on my overall experience.

Private Cloud

Other

My main use case for Bitrise is mainly for iPhone builds, mobile development, and mobile builds. It really helps.

I am mainly using Bitrise for iPhone workflows where it handles the certificates, signs the application, tests the build, and finally publishes it to the App Store. This is the whole workflow I am using.

In my opinion, the best features Bitrise offers are that it is easy to create workflows, support always helps us, and it can be used with a lot of different things.

When I say easy to create workflows, it is easy to build workflows because you can select a lot of built-in steps, so they can help you to come up with workflows easier.

Bitrise has positively impacted my organization because we can build the applications easier.

Bitrise has made building applications easier because it has improved the time we are spending on them. It is saving a lot of time. It is really easy for developers to build the applications because they can just invoke those workflows. This makes it easier to find the errors, improve the time, and improve the collaboration.

I think Bitrise can be improved because it is kind of pricey at the moment.

Regarding Bitrise's AI capabilities, I think its accuracy and reliability of output need improvement because from time to time the accuracy is low, but it is good overall.

I have been using Bitrise for four years.

Regarding Bitrise's AI capabilities, I think its governance and security are pretty good.

I would advise others looking into using Bitrise to just use them. My rating for this review is 9.

Public Cloud

Google

My main use case for Bitrise is for releases, deployment, and distribution for testers.

I have set up multiple workflows for Bitrise so we could be built depending on their repos, on their secrets, and on their specific environments. So we can build a dev environment, build UAT environment, or even production environment builds of our apps, and then it's distributed through Firebase App Tester to our testers.

Bitrise offers quite a lot of valuable features. One of the good features is the ability to choose the machines on which it will run. It also gives you workflow recipes to ease the setup of your CI/CD flow.

Choosing the machines and using workflow recipes in Bitrise just speeds up and frees developers' time, so even managers or testers themselves can choose the flavors and create builds for specific apps. They can do testing without interrupting developers. As for workflow recipes, they're helping to set up it and do some specific hookups to, if you write a message, 'smoke,' or something like that, it will hook up that it's a smoke build and will post in our Slack channel so everyone can see that a new build was created and similar things. Also, recently we have added functionality to post the release notes with the build, so it takes a specific amount of recent commits, and then QAs can see which task is in this build and should we be able to test those tasks with a specific build or we need to create a new one.

It helps us save some action minutes from GitHub Actions and we can use free time from the developer side to build new features or do technical debt and similar things. It just improves the whole workflow for everyone.

I think it could probably be higher, but we probably are not using all the features and functionalities of Bitrise ourselves, so it's hard to give a higher number because I think more features could be done with it, but we are just not using it.

I have been using Bitrise for four and a half years, close to five years.

Read documentation and try talking with Bitrise chatbot if you are stuck on some things. They usually are quite good at providing reasonable answers which will lead you on a proper way to solve your issues.

I would say on average, Bitrise saves probably about 15 minutes a day.

The review process was quite simple, easy to understand, and not too long, so it's not boring. I would rate this review an 8 out of 10.

Public Cloud

Other

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.

Private Cloud

Other