Bitrise vs Fabric: 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; Fabric: Simple, Pythonic remote execution and deployment. Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution..
Bitrise can be classified as a tool in the "Mobile Continuous Integration" category, while Fabric is grouped under "Server Configuration and Automation".
"Easy setup" is the top reason why over 10 developers like Bitrise, while over 19 developers mention "Python" as the leading cause for choosing Fabric.
Fabric is an open source tool with 11.4K GitHub stars and 1.73K GitHub forks. Here's a link to Fabric's open source repository on GitHub.
According to the StackShare community, Fabric has a broader approval, being mentioned in 147 company stacks & 38 developers stacks; compared to Bitrise, which is listed in 29 company stacks and 14 developer stacks.
What is Bitrise?
What is Fabric?
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 Fabric?
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.
We use Fabric for automating deployment and maintenance tasks: bootstrapping and updating application servers (using the "rolling update" pattern), pulling logs from the servers, running manage.py maintenance commands.
Automate everything! I have fabfiles for testing, bootstrapping, deployment, and building. Easy to customize and its pure python.