Goodbye Android builds. edit: yup; On March 1, 2018 buddybuild will stop servicing apps on the Free Starter Plan. Also on March 1st, the buddybuild service will stop supporting Android apps for all plans. Any historical data related to those apps will be deleted from the service at that time.
> Goodbye Android builds.
Think of it as an opportunity. Clearly this product has proved its usefulness, so there's a whole market to be served.
If anyone has a good Android (or even iOS) replacement, share here? I know myself and likely many others will be looking to migrate this month.
AppCenter.ms has many similar features and supports iOS, Android, Windows, ReactNative, Xamarin, and others. [Disclaimer: As I'm a PM on the AppCenter team I'll leave evaluation of goodness to others :)]
When is Cordova support going to land in App Center?
We use HockeyApp just now, and App Center's rather strange lack of Cordova support is a total deal breaker for us.
The logic still applies. 1. Start with platform you're most comfortable with. 2. Iterate on product until you have a winning formula 3. Replicate on 2nd platform to double revenues Building is a lot easier than identifying what to build, better to speedily experiment on one platform.
In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won't work well with RN), then deploy to both at once. We have had excellent results.
I rather use native UI code + C++ for business logic, use Qt or Xamarin than even bother with React Native.
Bitrise looks very nice for mobile apps. And it is open source https://www.bitrise.io/cli Are people interested in if we ingrate https://github.com/bitrise-io/bitrise in GitLab Runner so it works with GitLab CI?
We are happy to discuss it in more detail! DM me on twitter @birmacher
Awesome, I just followed you from https://twitter.com/sytses and I think I need a follow back before we can DM
I recently posted an „Ask HN“ asking for a flexible CI system. Most of the suggestions were proprietary hosted SaaS solutions. I was sceptical, and things like that keep me sceptical. Sure, setting up a CI system yourself is maybe a bit harder than using a hosted solution. But if the provider decides to change their offering, you are in big trouble. You‘ll need to spend a lot of time switching to a new sevice, migrat…
> Setting up a CI system yourself is maybe a bit harder than using a hosted solution. But if the provider decides to change their offering, you are in big trouble. I love how GitLab does it. It owns the parts watching your branches for commits and passing instructions to your machine, but the instructions themselves are a clean YAML file in the root of your repo, so if at any point you want to pack things and switch…
Yay, glad to hear that. And we're trying to make initial setup easier with Auto DevOps https://docs.gitlab.com/ee/topics/autodevops/ providing a default implicit gitlab-ci.yml file
Buildkite also offers free accounts to open source projects along with awesome email support. After years of Jenkins, followed by a couple of months trying to cherry pick CI parts of GitLab and make them play nicely with GitHub, Buildkite has been a breath of fresh air. Their service has allowed us to version control pipeline configs, test GitHub pull requests, and provide all core features without having to curate a…
We’re working on making GitLab CI work better with GitHub. I'm sorry to hear it will be too late for you.
I recently posted an „Ask HN“ asking for a flexible CI system. Most of the suggestions were proprietary hosted SaaS solutions. I was sceptical, and things like that keep me sceptical. Sure, setting up a CI system yourself is maybe a bit harder than using a hosted solution. But if the provider decides to change their offering, you are in big trouble. You‘ll need to spend a lot of time switching to a new sevice, migrat…
I have used (and set up) Jenkins, Drone and GitLab CI, and the latter two are definitely my preference these days. Unlike Jenkins, the configuration for Drone or GitLab sits in the repo, so it's as portable as the code itself - you manage the CI process through PRs and merges, same as anything. I use GitLab for personal projects, and it's pretty nice in that it's also git hosting, but the runners can be finicky to set up, and even though I've set up a few, it can still be confusing (specifically, tagging runners for specific tasks). In general, I think the most flexible thing is the one that's configured on the fly in the project itself.
If I were to seriously attempt to commercialize the toy apps I build for my kids/family I'd go iOS first easily. People with Apple devices are far likelier to pay, and Android development is, in my view, an inferior experience (although Kotlin makes it marginally less so these days).
This may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms. And if you also going to launch in EU/Australia/Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app. So the classical logic of implementing on iOS first doesn't really apply anymore. Now…
Is this referring to free apps, paid apps, or both? I've had a paid app on both stores for about six years now and in my experience the iOS version makes about 10x the Android version every year. Many other developers have reported a similar discrepancy.