You can go get it on the App Store! It runs on iPhones and iPads and requires iOS 13.
We appreciate everyone’s patience as we worked through the development process and look forward to hearing your thoughts and feedback.
Mike may see the development and launch of Dialog as taking longer than he would have liked, but from where I sit the app has come a long way in a relatively short period of time.
Back in May 2018 I linked to Dialog saying that it was “very much beta”. The current version is very much complete. I’m very glad the app exists.
Just updated to the Dialog 2.0 beta. Very, very nice.
In the early 2000s, when I switched to the Mac from Windows (oh how times change), SubEthaEdit was an amazing leap in text editing. It allowed you to connect with other Macs to collaborate on the same document — something we take for granted these days.
Here is Dominik Wagner, one of the original authors and now maintainer of SubEthaEdit, on the inception of this particular feature:
Luckily one of us dug up an old Xerox Parc Paper that showed how latency free live collaboration can be done. At that time it fit perfectly with the newly released Bonjour technology to allow for networking without configuration between Macs. That was super exciting and we quickly got to a point where we could see this technology as viable and so we went on to build our application.
The latest version of SubEthaEdit is free and open source. It brings back a lot of memories seeing this.
You can use all of the app’s features for free with only two limitations: a watermark in the lower left corner and a 30-second limit for video exports.
Matt Haughey vents his frustrations with WordPress:
Over the past week I’ve written a bunch of posts while out and about using the iOS WordPress app, often with photos of things I was seeing. But unless I was on WiFi or had 5 bars of LTE connectivity, I would get a Posting Failed, Retry? message. The wild thing is even after hitting retry a bunch, it would still fail. And then if I flicked over to my draft posts folder, the post wasn’t there. If I didn’t keep retrying and instead clicked anywhere in the app, the post would disappear completely.
Like Haughey, I too am frustrated with the WordPress mobile app (I’m on Android, and I have the same issues). I’ve actually removed WordPress from my phone because I can’t use it. It simply doesn’t work well at all. If I even try do post my photo posts with it crashes over and over and over and over. Which is why you’ve seen a lot less photos from me.
Earlier this year, we surveyed Xamarin.Forms developers about the kinds of custom controls and extra platform code being written repeatedly that should be considered for support “in the box”. From these conversations, we created an initiative to deliver as many as we could in the next several releases. Just six weeks after shipping Xamarin.Forms 3.0 at Build 2018, we are excited to introduce Xamarin.Forms 3.1 with a batch of those enhancements to make your lives easier.
I shipped a Xamarin.Forms app on iOS and Android in 2017. I thoroughly enjoyed exploring and using Xamarin and in some circumstances, for some teams (especially those with deep C# experience) I’d wholeheartedly recommend Xamarin. The Xamarin team continues to keep on top of the latest OS/SDK/API releases as well as making it very easy for developers to ship cross platform applications.
Hopefully by the end of this year I’ll be able to say the same about React/React Native. I’m looking forward to exploring this deeper than I have in the past. I like to use different things so that I know what the best tool for each job is – rather than using the same tool for every project.
At launch, the app makes available a number of features you’ll be familiar with from using the Micro.blog service including being able to view your timeline, your mentions, and the Discover page. Currently, you are unable to create a new post. This is planned for a future release.
The current app is very much beta, but you can immediately see the potential for the usefulness of this app. I’m looking forward to seeing how this one matures.
Trying out Blogo.
Apollo is built by a former Apple employee with feedback from thousands of Redditors to sculpt the best client possible. It features a beautiful, native iOS design, smooth, customizable gestures, fast loading pages, a supercharged Media Viewer experience, a powerful, full Markdown editor, a Jump Bar for lightning-fast navigation, and so much more. You have to see it to believe it.
This is easily one of the best iOS apps I’ve ever used. Even if you don’t use reddit often it is worth having for wasting time on reddit.
The idea for Summit came nearly 4 years ago as far as I can tell. I’ve hunted around for scraps of paper, digital notes, code snippets to see if I can come up with an exact date but I’ve been unable to. And it has been fits and starts for several years.
When Kyle Ruane and I started on the idea we first thought the UI would be a bit more game-like. I envisioned a 3D model of the current mountain you were hiking that would progress the person up the summit in first-person towards each goal. This was altogether too much work, and far too difficult given my unfamiliarity with the platform. Kyle’s suggestion – again, many years ago – was to use a low poly look. He would craft a low poly representation of the summit and we could allow the user to move around in it, perhaps even spin it around, zoom in-and-out, etc.
I pulled that thread for a very short time before giving up. Remember, we started toying with the idea of Summit before Swift was released. So I was trying to draw this UI with Obj-C. Something I’m even more terrible at than Swift.
Here is what one attempt at drawing progress lines using Obj-C looked like back 4 years ago or so. I took this screenshot in June 2014 and was already labeling it “historical junk” in my files.
The red triangles were goals to meet, the blue line was your path, and the white line was your progress so far. My goal was to overlay this on top of the low poly art that Kyle drew. This was inspired by maps like this. (copied here for archival purposes)
This worked but was not that easy to pull of, introduced more complexity than we needed, and so we quickly shelved the idea until we got more familiar with the platform.
In tandem I began constructing a simple web UI to start cataloging steps from a phone. This was purely to get used to writing code that would track user’s steps, show stats, work on our step algorithm (the code that determines how far up Mount Everest a single step walking in a downtown city parking lot gets you), etc.
It went this way for a few years. I would open up a code editor and begin working on the pieces of Summit; the progress UI, the algorithm, the code to read from a user’s step count or HealthKit or Apple Watch.
In June 2017, when I picked up this project on my own to take on since Kyle had moved away, I decided I needed a simpler approach to the UI. In part because Kyle is the design genius but also in part because I wanted to get as quickly to shipping an app as I possibly could. I prefer to iterate on ideas with user feedback than to work on something in a silo for years. I wanted a way to show the summit, or some visual from the summit, but yet also show one’s progress. And I also still needed multiple goals per summit.
Here are a few drawings from this summer.
See, I’m not an artist. Admittedly, though, this wasn’t an attempt to draw anything beautiful but rather to get a general idea for all of the views I needed to pull off the layout. I needed some labels, some buttons, navigation, etc.
The long goal buttons was really “a punt” on my part. I gave up trying to get Xcode’s Storyboard feature to properly align a changing number of goal buttons (since each summit has a different number of goals) in a way that worked with each device size. It was very frustrating. So I began to go down this path of having them just be full-width, flat buttons.
But then I ran into Brian Voong on YouTube. In most of his video tutorials he suggests forgoing the Storyboard feature and using code to create the UI. Though I didn’t want to lose the progress I had made, I’m so glad that I took his advice. Writing UI directly in Swift is far, far easier (for me) and seemingly more powerful than using Storyboards.
This revelation allowed me to go back to a drawing I did a month earlier. This one:
On the left, the elements needed, on the right, a rough sketch of a much more minimal and airy design of the current summit view. The goal buttons have varying distances between them relative to how far apart they are in real life (I’m still working on getting this right in the app).
Using Swift I was able to make this happen much easier than Storyboards.
The above is one of the very first swings at this view. It had all of the elements I wanted. And I’ve been iterating on this specific design ever since. I wish I had the hundreds of iterations saved but I don’t.
Here is what the most recent iteration looks like with goal buttons that are easier to determine your progress and other tweaks to make the UI more consistent.
This is the design for this view I’ve settled with for now. I have plans to iterate on this current design for some time before, perhaps, taking a whole new swing at it. Perhaps my skills will grow to the point that I feel confident going back to Kyle’s low poly idea. But, I’m pleased with how it has come along so far.
Mac users can use the native Micro.blog for Mac app. It’s a free download and supports most of the same features as the iOS version.
You can see a short video of it on Manton’s blog. You’ll even notice a rather handsome avatar make an appearance.
Unfortunately I cannot give this a spin yet since I haven’t upgraded my Mac to High Sierra. And it doesn’t appear I’ll be doing so for at least a month or two since I haven’t seen any updates from Apple on that front. High Sierra just seems far too unstable to switch to on my main work computer at the moment.
Colin Walker, though, seems to like this new app:
Manton has repeatedly said that this is just a version 1.0 app but, I have to say, it’s been rock solid. Browsing, replying and posting to the blog have all been a breeze and I’ve not had a single issue or error.
Portrait video compilations made easy—that’s what SnapThread is all about.
Like SnapChat without the network. I’ve long held that SnapChat and Instagram have the best UIs but it is a shame they aren’t just an app. Apple tried to solve this with Clips but that is only square-crop. This app could be very useful.
I’ve been steadily working on Pedometer++ now for nearly four years. Over that time the core conceit of the app has remained the same, to motivate you to be more active. It has done this with colors, confetti, complications and streaks. Now I’ve added another tool to hopefully motivate, achievements!
Pedometer++ continues to be my favorite step counter*. I’m looking forward to trying out this latest release.
* Yes, I’m building Summit, but that doesn’t mean I won’t still use Pedometer++ and Map My Walk. Each of these apps play a different role. I hope to make Summit good enough to fill a role for others too. But not the same role as Pedometer++. Even though the number one feature request is that I add more stats – that isn’t what Summit is about.
I’ve thoroughly enjoyed the time I’ve spent beta testing Summit and look forward to the new builds.
Colin has provided excellent feedback on Summit. So have so many of the beta testers. I too am looking forward to publishing new builds.
If you’re on the beta list (which you can get on by putting your email address in the form on this page) and you haven’t gotten Build 15 yet – please let me know. Build 16 is due mid-September.
I’ve stitched together a temporary web site for the app as well as a mailing list that will allow you to get access to the final few beta builds prior to public release. If you have an iPhone please consider signing up and giving it a spin. I’d be very grateful for your feedback.
Thanks to the 13 private beta testers who have already tested the app and provided feedback. You can expect a brand-new build of the app coming in September.
Summit is a free, iOS-only app that uses your step count to virtually hike up tall peaks like Mount Everest in Nepal, learn about amazing landmarks like Diamond Head in Oahu, and even take a leisurely stroll down famous streets like Lombard Street in San Francisco. As you make progress on your journey you’re provided new information at each goal.
At the time of public release there will be 5 summits and new summits will be added each month thereafter.
Here are some screenshots of the app as it is currently:
When I started on Summit I did not know how to develop an iOS app. It has been really fun to learn Swift, Xcode, iTunes Connect and Test Flight, and the myriad other things I was able to learn in order to get this app as far as I have.
I still have a bit of work to do, but I’d love your feedback along the way as I finish the app up for release.
With one massive update we’ve brought everyone’s favorite file-transferring truck into the future with more speed, more servers, more features, more fixes, a better UI, and even Panic Sync. Everything from the core file transfer engine to the “Get Info” experience was rethought, overhauled, and improved.
Hard to believe Transmit 4 is over 7 years old.
In early June I decided I wanted to learn iOS app development using Swift.
I’ve made a lot of progress over the last month, building two apps that I can use on my own phone, and one app that I’m now in beta testing via TestFlight with a few friends. Over the last month I’ve made some observations on the process of building an iOS app, the Swift programming language, Xcode, iOS frameworks, and the various other bits needed to make an app. I thought I’d take the time to jot those down.
These are in no particular order:
Overall I’ve had a positive experience learning to build an iOS app on my own. Going from having an app in TestFlight to shipping an app feels like preparing to cross a desert on foot. But, I’m enjoying my experience so I’m going to trudge forward to do so.
I hope to ask for public beta testers of the app in a few weeks or a month.
Under Armour has a free app called mapmywalk that I’ve been using to map hikes that I’ve been taking recently. I really like it.
It doesn’t rely on street maps but rather exact GPS coordinates to map the route I take. This helps me to map trails that I’m hiking that aren’t on any park maps so that I can track the distance I’ve hiked, the trails I’ve already taken, and more. I like to explore new areas and this app is useful to know where I’ve already been.
One other nice feature is that it gives me audio updates while I am hiking at each mile I cross to tell me my current pace and time. My hiking goal isn’t to set a pace or go a particular distance (at least not lately) but this does give me a cue as to how long I’ve been wandering around. I can easily burn a bunch of hours so this app keeps me moving forward so I’m not stumbling around for hours and hours.
Thanks to the team behind this app for making it useful.
Introducing Clips. A new iOS app for making and sharing fun videos with text, effects, graphics, and more.
I’ve been looking for an app like this for a long time. The Verge describes how I think I’ll use this app.
My best guess is because the default camera app is still something that’s supposed to be super simplistic (and accessible from the lock screen). And I think in some ways, this is a precursor to a consumer AR app, but Apple declined to answer questions around that. Clips seems like it could be the perfect app to use when iMovie is too much and the default camera app is not enough. The question is whether it will be the necessary stop between your phone’s camera and your favorite social network.
I’ve tried to edit a personal “vlog” (that I do not publish publicly) for a long time. And I did it using iMovie. But iMovie is too much for this. What I really want is Instagram Stories or Snapchat Stories in their own app. It looks like I’ll kind of sort of get that with Clips.
I don’t know why they didn’t just release it. Apple doesn’t usually announce things before they’re ready (I’m not counting operating system releases which require so much public testing). But I’ll be happy to get my hands on this next month.
No closed-source code will be embedded in Overcast anymore, and I won’t use any more third-party analytics services. I’m fairly confident that Apple has my back if a government pressures them to violate their customers’ rights and privacy, but it’s wise to minimize the number of companies that I’m making that assumption about.
Marco has always put his money where his mouth is. This is just another demonstration of that.
These indie apps are often marketed as beautiful, wholesome alternatives to grimy corporate or open source software, but how could I possibly rely on these products for essential tasks like note-taking if they’re just going to disappear out from under me in a few years? The idea that software has a lifespan controlled by the developer is, in my opinion, toxic to the market. It’s just one of the many things pulling the App Store down, and one of the many downsides of living in a walled garden.
I have to agree. More and more I’m inclined to use an open (but not necessarily free) alternative for just about any app or service that I rely on.
I wasn’t a Vesper user, but if I was, I’d be scrambling to find an alternative since it is now being shut down. I’m a happy Simplenote user which is free and open and backed by a company that wants to keep things open and running for as long as possible.
Picturelife’s recent closing, which I called in January of 2015, is also a stark reminder that even if we rely heavily on an app or service, and even if we support it with our money and our word-of-mouth, it doesn’t mean that it will stick around.
If you find yourself relying on an app or service that could disappear tomorrow do yourself a favor and seek out alternatives while you still have plenty of time to make the switch. You don’t have to switch, but knowing what alternatives are out there and having a plan can save you a ton of headaches. If I hadn’t switched from Picturelife to iCloud when I did I’d be hurting right now. Bigtime.
I’ll have more on Picturelife’s shutdown in a future post.