iOS Developer Senior at a tech vendor with 10,001+ employees
Real User
Top 20
Jun 30, 2026
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.
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.
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.
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.
Tech lead dev ops at a outsourcing company with 1,001-5,000 employees
Real User
Top 20
Apr 30, 2026
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.
Senior Software Engineer at a tech services company with 501-1,000 employees
Real User
Top 5
Apr 30, 2026
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.
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.
Bitrise offers an advanced platform for mobile app developers seeking efficient CI/CD solutions, known for streamlining processes and enhancing productivity.Designed for mobile application development, Bitrise provides seamless integration with popular tools, ensuring a high level of automation. It caters to developers looking for simplified workflows that accommodate modern mobile development demands. Users benefit from an intuitive dashboard that supports rapid iteration and testing,...
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.
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.
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.
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.
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.
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 think Bitrise could be improved if it was easier to generate Android QA and iOS at the same time.
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.