phillipcaudell

This is something coming in a later release (Groups)

A native looking webpage for a native looking app :-)

Hi I’m the creator of Big Mail. As the subscription is sold and managed by Apple we’re bound by the App Store terms and conditions (things like refunds, liability, etc)

There's a newer board that uses a single USB-C cable, but it's a bit more expensive: https://www.aliexpress.com/item/4001084086628.html?spm=a2g0o...

This is correct! Though there is a newer driver board which supports USB-C (and thus one cable), but it's a lot more expensive. And since I was connecting to an 2015 iMac, wasn't needed in my case.

The supplier was great! I think I received it within a week of ordering (which considering I'm in the UK and it was coming from mainland China is pretty impressive). Here's a link to the exact part and supplier I used: https://www.aliexpress.com/item/4001192011831.html?spm=a2g0s...

Tape and glue is literally how iMac panels are held on https://www.replacebase.co.uk/for-apple-imac-a1419-27-lcd-gl...

Heya, I’m the guy who put this together. Let me know if you have any questions about it! I’ve had the setup for about a month now and absolutely love it.

Cheers for the feedback - I'll look at tweaking the copy. I've had a sinking feeling it wasn't as crystal clear as it could be (too close to it).

Hey all!

I've been working on Roboto for some time now after leaving my full time job as an app developer and designer.

One particular pain point was getting beta builds to our testers and deploying to the App Store. We worked in a team, so creating builds would require checking out each other's changes, ensuring we had the right profiles on our machines, and so on. Yuck.

You might be thinking "you need to use CI - Jenkins!", and we tried it. I was at an agency with multiple apps on the go every few months, and getting Jenkins set up and working in a way we wanted was a massive pain in the ass. It was a hot mess of plugins, hacks and external services such as TestFlight and HockeyApp. Other services that offered an alternative — such as Travis and CircleCI — would require access to your private source code, signing identifies, etc.

Paying someone else to compile your code made little sense to us, as we had perfectly capable Macs of our own. Roboto is built so that we manage the bits you'd want us to manage: hosting of the IPA and APK packages, installation pages, emails, web interface, users, etc. You then run the "Roboto Worker" on a Mac of your choice, which does all the compilation and source code management locally. The upside of this is we never see your private data, and your builds can make full use of your hardware — no sharing with other developers

We have big plans for Roboto. What you see today is just the beginning. Whilst I think sharing future plans publicly can sometimes set people up for heartbreak (scrapped features, delays, etc), here's a couple of things already in the works:

- Unit test support. - iTunes Connect and Play Store management (metadata, screenshots, etc) - Full build support for Android.

So that's a bit about why Roboto exists. I'm really looking forward to seeing what you guys think! Happy to answer any questions you guys and gals have. Thanks!

tl;dr: It's an out the box CI tool for mobile apps, TRY IT FREE TODAY.