Bitrise vs Greenhouse: What are the differences?
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; Greenhouse: Simple and secure continuous integration for mobile apps. Greenhouse automatically builds your project for every commit you make and runs all your unit or UI tests on the emulator/simulator or on real hardware. Automatic build distribution is also supported so that your team and clients are always up to date with the latest state of your apps.
Bitrise and Greenhouse can be categorized as "Mobile Continuous Integration" tools.
Some of the features offered by Bitrise are:
- Continuous Delivery
- Hosted Environment
- Customizable Workflows
On the other hand, Greenhouse provides the following key features:
- Supports Android, iOS, Cordova & Ionic apps
- Free for up to 2 public or private repositories
- Android- Gradle projects, iOS- Xcode build system and Facebook xctool, with full CocoaPods & Carthage integration.
"Easy setup" is the top reason why over 10 developers like Bitrise, while over 11 developers mention "Easy setup & usage" as the leading cause for choosing Greenhouse.
What is Bitrise?
What is Greenhouse?
Need advice about which tool to choose?Ask the StackShare community!
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 Greenhouse?
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.