Bitrise vs Distiller: What are the differences?
What is Bitrise? Automate your mobile app development from building through testing to deployment. In short Bitrise is a Continous Integration and Delivery (CI/CD) Platform as a Service (PaaS) with a main focus on mobile app development (iOS, Android). You can automate the testing and deployment of your apps with just a few clicks. When you trigger a build a Virtual Machine is assigned to host your build and your defined Workflow (series of Steps scripts) will be executed, step by step.
What is Distiller? Build and deploy iOS apps faster. Distiller's hosted continuous integration platform takes the pain out of mobile development through automated build, test, and deployment of your iOS apps.
Bitrise and Distiller belong to "Mobile Continuous Integration" category of the tech stack.
Some of the features offered by Bitrise are:
- Continuous Delivery
- Hosted Environment
- Customizable Workflows
On the other hand, Distiller provides the following key features:
- Integrated with GitHub
- Rebuild and test with every commit
- Automated OTA deploy via Testflight & Hockey
What is Bitrise?
What is Distiller?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Distiller?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Bitrise?
What are the cons of using Distiller?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.
We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.
You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.