Matthew Lang

For a long time, I’ve been a user of Path. A social media network for those who want a level a level of privacy. It was another Twitter or Instagram but only for those that wanted to keep their timeline limited only to a few people.

In a time when everyone was sharing everything and anything, it was great to see a product that changed it’s approach to sharing.

I was happy for a few years there. Sharing moments with the family and knowing that anything I shared there would be private.

As other social media networks started to move on with new features, it felt like Path was falling behind.

To make themselves relevant again, Path split their app into two different apps. One for sharing to your timeline and another for messaging. The messaging feature was simple, but the decision to share the messaging to a separate app just looked crazy. At the time I already had many other messaging apps. I didn’t need another.

Thankfully, they’ve since merged the two apps again.

Then Path decided they needed a little extra money. So they decided to launch a subscription tier that would include a bunch of stickers on your account so that you could, you know, put stickers on your posts and comments on Path. It’s not the kind of feature that I would want to pay money for, but that’s what they were offering.

As time marched on, I slowly reduced my posting frequency to Path and instead opted for an Instagram account. Despite my preconceptions about it, I’m happier posting stuff on Instagram than I ever did on Path. The whole experience is spot on for me, and there are very few elements of the social media network that I don’t like. I even use it for messaging with Jennifer and family in Canada.

Having not posted to Path in some time I revisited the app a few weeks ago and discovered some changes.

First, you can now share stories on Path, much like Instagram and Snapchat.

Secondly, you can now share your Path moments publicly and even follow other people, even if you don’t know them. There is still a level of privacy with Path, but it appears to have been eaten up by the need for Path to be a competitor with Instagram.

With Path changed so much in the last few months, I’ve entirely stopped posting to it and now post to Instagram which in turn, posts to my micro-blog.

My problem with Path isn’t that they’ve started charging for a premium tier, it's a fact their now another Instagram clone and sharing many of the same features that Instagram has. I don’t need another Instagram but nor do I need Path these days. I’m happy to share moments on Instagram, and that’s it.

I never thought I would see the day where I would be dissing on Path, but their recent changes have been features that I will never use.

The last nail in the coffin for me and Path though is that you can’t export your content from Path in any form. I emailed Path’s support team about this. They answered that I should disable my account. Not what I was hoping for, by my request for an export facility has been passed onto the Path team, but I’m not holding my breath for it to appear anytime soon.

While it was my intention to write about my web development workflow on my iPad Pro at a later date, one of my readers got in touch asking about how I use the iPad Pro in this capacity. Rather than hold off I thought it would be a good time to elaborate a bit on my workflow when using the iPad Pro for web development. What follows is still under review and isn’t my first attempt at using an iPad Pro for web development.

My first iteration on using the iPad Pro involved the Blink app and setting up a remote development environment on a DigitalOcean server. This took a while to setup but even then I found that using Vim as my text editor on a touch device didn’t work for me. So it was back to the drawing board and what follows is a second pass at putting together a web development environment for the iPad Pro. It certainly isn't final but it’s working for me now.

Another point to consider is that this web development environment is tailored towards Ruby on Rails development. A similar setup will work for other languages and frameworks providing you can run your development environment locally in iOS or on a platform like Heroku or Engine Yard.

Remote services

I'm using a number of remote services not because I need too just to be able to work on an iPad Pro, but because they're already part of my workflow on the desktop and I can use them on the iPad Pro as well.

Github

I’m using Github for source code management for a number of reasons like client familiarity, Heroku integration and a few other reasons. The main reason I'm using Github though is that it's tried and tested. You can't argue with that.

I've tried a number of source code management services like Gitlab and Bitbucket. While there are benefits and drawbacks to each service, Github is my preferred source code management service.

Heroku

Heroku has been my go to hosting platform for Rails applications for a long time now. I’ve tried other platforms and while they might be good fits for particular clients with specific needs I’ve found that Heroku has everything that I need for hosting most Rails applications.

I’ve already mentioned that github is good for Heroku in that it’s baked into the pipeline service that Heroku offers. Automated deploys are a great thing and using this in conjunction with Heroku’s CI tool is one less thing for me to configure.

Client side apps

With our remote services in place it's time to focus on the client side apps. Apps that focus on developer productivity have largely revolved around other things that developers do like project management, issue tracking and documentation but there are more text editor apps becoming available on iOS and I’m confident that there will be even more apps like this overtime.

Working Copy

I’m using Working Copy as my local Git client. I’ve been using this for a few months now. It's easy to setup and it works well in iOS 11 with split view and the drag and drop functionality. Working Copy also integrates well with GitHub, Bitbucket and Gitlab. So I’m not tied to using one particular Git source code hosting service.

Text Editors

And now the essential bit of kit for any developers toolbox, the text editor. I’m running two text editors at the moment with the hope of selecting just one of these when I’ve given each of them a thorough test.

Textastic

I’ve used Textastic in the past but only as a means to edit text files remotely. Using it now as a text editor means that it needs to tie in with Git, have the essential settings I need for editing source code and perhaps the most important feature of all, a nice colour scheme!

So far I’m pleased with its feature set and there’s been little in the way of blocks when it comes to workflow. Once I had Working Copy setup to track my Github repos, I was able to drag a branch into Textastic and start working. Changes to files are marked in Working Copy so that you can commit your changes as you normally would.

Textastic doesn't have all the preferences of a desktop text editor like Sublime Text but the essentials are there. Editor themes, font selection and size, and tab size and type. There's also find and replace and symbol listing which is handy for larger source code files.

Textastic is working well for me but the one thing that I would like to see a easier management of the files I'm working with. A command pallete like Sublime Text would be a nice addition.

GoCoEdit

GoCoEdit is a new addition to the test. While Textastic I have history with, GoCoEdit is fairly new and I’m still finding my feet with it. It shares many of the same features as Textastic though, so it's easy to get started.

Like Textastic, you can drag and drop a repository from Working Copy into the app to get started working. Changes to files are marked in Working Copy for you to commit.

Editor themes, font selection and size and tab size and type are supported as well. There's also find and replace functionality as well. I've also found that in GoCoEdit there is a command pallete with limited functionality. You can manipulate text, find and replace text and save a file using this but there's not much else you can do with it.

I must admit, I do prefer working with GoCoEdit over Textastic. Saying that though there isn't much between them and both are more than capable of being all-day text editors if you find you have to work on your iPad Pro for the full day.

There are many things missing from these editors that would be taken for granted in a desktop text editor like Sublime Text but apps like this are still relatively limited in what they can do on a iPad. The most essential features are there though.

Adapting

If there’s one thing I’ve learned from all this is that if you’re going to use an iPad Pro for web development or any other form of work then expect to adapt to a new range of apps. Sure you’re preferred apps might be available on iOS but the interface does require you to adapt to the new environment.

Thankfully iOS is getting there with better features like the split view and drag and drop. Features that we’ve taken for granted in desktop operating systems for years but are only starting to see in operating systems like iOS.

My web development workflow has required some changes for the iPad Pro but it’s nothing drastic and a bit of learning on a new device isn’t a bad thing.

Thanks to Curtis McHale for reaching out to ask about this and giving me that much needed nudge to write.