Further, while buddybuild is favored by thousands of because it can can auto-provision iOS devices for you on the fly.
Meaning, you never have to deal with provisioning profiles and UDIDs ever again.
We also care deeply about making sure that teams can involve and engage their end users as part of the development process. One of the reasons we built buddybuild is because of the frustration sending builds to our users... AND then never hearing back from them. Phones are great devices for "consuming content", but it became obvious that the physical form factor of the device tends to result in infrequent feedback which was often ambiguous.
So, we build an SDK that gives you high quality and actionable bug reports from beta users. With a simple screenshot, testers can file bug reports that include graphically annotated screenshots, feedback notes and their device metadata.
We also have a feature called "Instant Replay", which lets you watch a video of the exact steps required to reproduce a crash. Instant Replay works in conjunction with our Crash Reporting solution to offer you both the exact lines of code that caused a crash as well as the exact sequence of events that lead up to it (https://www.buddybuild.com/blog/introducing-instant-replay)
Thousands of teams with fairly complex needs use buddybuild every single day. They teams like Slack, Meetup, FireFox, Wordpress and others..
Could it be that your service is more suited for people working with React?
In a slightly related note, I find it hilarious that people are using a framework made by a company behind what is probably the most hated mobile app ever.
We're a mobile focused continuous integration and deployment solution.
When deciding which platforms to support, we looked at current adoption for Native iOS and Android (this was no brainer), Hybrid (PhoneGap, Ionic, Cordova) and "emerging" platforms (React Native, Xamarin).
Ultimately, we decided to prioritize the others first. CI/CD service is applicable to any mobile development team.. but to your point, buddybuild is better suited to those other platforms, as those are the only ones we support.
In our experience (which also factors inbound requests), Xamarin is still relatively nascent as compared to the others.
That said, you can should expect to see Xamarin support soon :)
Also, fwiw, Microsoft purchased Xamarin only recently.
But this puts your first statement in a completely different light ;)
I should also note that React Native was announced in 2015 while Xamarin was announced in 2011 (with Miguel's work on Mono being much older). Can you then call Xamarin an "emerging" platform?
Buddybuild's crash reporting functionality just got even better.
Instant Replay answers a common question amongst development teams - "how did that happen?" - by showing devs a video replay of exactly what a user was doing in the moments leading up to a crash, which means the dev gets an exact set of steps needed to reproduce it.
You shouldn't notice a webhook deluge because the site isn't generating events. I'm watching our webhook services though and will let you know if that changes.
At a high level, Buddybuild is a mobile focused continuous integration, continuous deployment and user feedback solution that takes minutes to setup.
We want to help mobile developers build better apps, faster. To do so, we've built an end-to-end system that unlocks a simple workflow: a simple 'git push' to build, deploy, gather feedback and iterate.
As we tried using existing solutions, we felt that there was an unnecessary amount of complexity involved in creating builds, getting those builds to users and then getting meaningful and actionable feedback from those users.
If you're an iOS developer, you'll never have to manage new devices, UDIDs, provisioning profiles or signing identities again. New testers and their devices are automatically provisioned on your behalf through buddybuild.
Further, buddybuild’s deployment service can deploy instantly on every build, every night, or at the push of a button.
By simply taking a screenshot, testers can send graphically annotated screenshots and feedback notes. If your app crashes, buddybuild will trace back and highlight the exact line of source code that caused the crash, tell you which users were affected, and how many times the crash has occurred.
Finally, get a heads up on any potential breaking changes in Xcode. Within 48 hours of the release, buddybuild automatically takes your most recent successful build, builds and runs tests against the latest version of Xcode (including betas!) and emails you the results.
Of course, built in integrations with your favorite services - GitHub, BitBucket, GitLab, Slack, JIRA Pivotal Tracker, Slack, and HipChat.
With buddybuild, you no longer need to cobble together disparate systems to be able to iterate quickly on mobile.
Nice to see BB here! We used BB to build our iOS app; over 3 months, it made the process of iterating, deploying and collecting feedback on our prototypes incredibly easy. Great product and a very proactive team. One feature that BB has that is particularly useful is the ability to deploy test builds to various groups. We deploy a build internally to our team group at least once daily, and then another more polished version to our most avid beta-testers at least once a week.
We don't think of it as an either/or (In fact, buddybuild supports deploying directly to Testflight as well).
Buddybuild's deployment really comes into its own earlier in the dev cycle
- when you want to deploy to your internal team (who might want to jump to old builds or different branches)
- when you want to schedule deployments (every evening for example)
- or when you want to send a build very quickly to someone.
We've made the onboarding experience for new testers very simple - automatically handling adding UDIDs to provisioning profile. Also, not having to install a separate app is very appealing to some people.
Do you have/plan integration with Unity3d platform?
My app has client and server, and often, both has to be released simultaneously. Server has dev/test/beta/production deploys w/ different databases, correlated to dev/alpha/beta/store in Google Play and dev/internal/external/store in iTunes connect. Server URL for each stage/build is embedded in the binary. Can your platform handle deploying not only client, but server as well?
I think Unity is something we'd love to support in the long term. I don't know what the timeline on the would be though.
We already have people who are using buddybuild to co-ordinate deploying mobile and server apps (either a full environment or something like Parse's Cloud Code). I've also seen people spin up a local server environment for running iOS Simulator tests against, so their entire stack can be tested.
We use buddy build pretty actively. It's a Game Changer! It took about 2 minutes to get up and running and we have a free CI process for all our builds. I particularly love the automatic upload of symbol files for error tracking. BB is a big win in my book!
We use the spaceship gem, but none of the fastlane cli tools.
One of the things we really wanted to enable was an incredibly simple set up process, but while balancing that with giving a developer the ability to work in the way they want to work.
So while we automatically handle most of the common situations, there's always the ability to run custom scripts and do whatever you want to do. Many teams are doing interesting things like this.
