• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

John August

  • Arlo Finch
  • Scriptnotes
  • Library
  • Store
  • About

Weekend Read

Making the App Store better

April 23, 2014 Apps, Bronson, FDX Reader, Highland, Weekend Read

Roughly this time last year, I wrote about how the App Store encourages [topping the charts and racing to the bottom](http://johnaugust.com/2013/topping-the-charts-and-racing-to-the-bottom), and how that hurts both developers and users.

David Smith has compiled a list of recommendations for [making the App Store experience better](http://david-smith.org/blog/2014/04/16/towards-a-better-app-store/). I especially agree with several of his suggestions:

> 1: Apps should be required to pass approval on an ongoing basis.

I’d go further and say that if an app has had no activity for a set number of months, it automatically gets de-listed. I suspect more than half of the apps in the store are effectively zombies, abandoned by their creators. These apps’ only function is to clutter up search results.

> 6: Make the process of applying for a refund clear and straightforward.

> Right now you go to reportaproblem.apple.com and then fill in a form. I’d love to see this integrated into the App Store app itself. Perhaps even into the Purchased Apps area.

Roughly 10% of our support emails are from people who really should just get a refund because they bought an app without really understanding what it did. We have a boilerplate email that walks them through the process of applying for a refund, but there’s no reason it needs to be so complicated.

I think prices for some apps could easily and appropriately rise if customers understood they could get their money back if unsatisfied.

> 11: Make the rating scale a rolling, weighted average rather than just current version, at least soon after updates.

We update our apps very frequently, sometimes twice a month. Each time we do, our ratings drop back to zero, effectively punishing us for improving the app.

A rolling, weighted average would better reflect not only how satisfied users are with the current version, but with the product overall.

In the iOS App Store, our products are [Weekend Read](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8) and [FDX Reader](https://itunes.apple.com/us/app/fdx-reader/id437362569?mt=8). FDX Reader is old — it hasn’t been updated in a year — but we’re keeping it around until the iPad version of Weekend Read.

By my criteria, should FDX Reader be dropped from the store? I don’t know. It still sells, and we haven’t gotten a support email for it in months, so users are apparently satisfied with it. But if we got a warning email from Apple saying it needed to be updated or face de-listing, we’d pay attention. More than anything, that’s what a regular review process would achieve: making developers take another look at their old apps.

For iOS, we also have the [Scriptnotes](https://itunes.apple.com/us/app/scriptnotes/id739117984?mt=8) app, but it’s made by [Wizzard Media](https://itunes.apple.com/us/artist/wizzard-media/id318848960?mt=8). We release it under the Quote-Unquote label only so we can track downloads.

In the Mac App Store, our products are [Highland](https://itunes.apple.com/us/app/highland/id499329572?mt=12) and [Bronson Watermarker](https://itunes.apple.com/us/app/bronson-watermarker/id481867513?mt=12). If you look at the current Bronson reviews, there’s a one-star review from a customer who couldn’t figure out the app. He didn’t write us for support; he didn’t check any online documentation. He’s exactly the kind of user who should have been able to click a button and get a refund.

I hope at this year’s WWDC, we’ll see Apple taking some of Smith’s suggestions to make the App Store experience better.

Weekend Read knows what page you’re on

April 18, 2014 Apps, Weekend Read

screenshotJust in time for the weekend, we have an update for Weekend Read. It’s [free in the App Store](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8).

Version 1.0.4 adds a page count in the footer of the reader view, so you’ll always know where you are in the script. Both Rian Johnson and Aline Brosh McKenna asked for this, and I do as I’m told.

Actually, the page counter is really helpful. I don’t know why we didn’t do it in the first place. Obvious in hindsight, and so forth.

Weekend Read 1.0.4 also improves parsing of some FDX and PDF scripts. If you have a file that didn’t work right in an earlier version, delete it and reload it. There’s a good chance it’ll work. ((To keep things snappy, Weekend Read does the bulk of its processing magic as it’s first importing the script. When we change out the parsing engine, it doesn’t retroactively go back and try to reinterpret file already in your library.))

Finally, Weekend Read now properly hides Fountain notes [[in brackets like this]].

We have a lot more in the works for Weekend Read, but we didn’t want to hold back these small-but-useful improvements.

logoIf you’re looking for something great to read this weekend, we have six episodes of Party Down available as our Featured Show, along with an introduction by showrunner John Enbom. Trivia: The Valhalla catering company, introduced in the gay wedding episode at the end of season one, was inspired by the ridiculously good-looking cater-waiters at my wedding.

Folders, tags, and keeping things tidy

March 25, 2014 Apps, Weekend Read

library viewYesterday, two users separately asked for folders in [Weekend Read](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8).

It’s something we’re considering, but it’s a significant UI challenge, so I thought I’d talk through some of the issues in blog form.

In Weekend Read, one of the main views is called the Library. Here you see a list of all the scripts and other files you’ve imported.

These files are “inside” Weekend Read on your iPhone, both conceptually and programmatically. That means that if you’re offline, the files are still there. If you modify the original file in Dropbox, the version in Weekend Read is unchanged. If you delete the app, you’ve deleted these files. Most users seem to intuitively understand this setup.

The challenge comes when a user wants to keep 10, 20 or 50 scripts in his Library. We offer the ability to sort the list (Recent or A-Z), but there’s no way to keep the Library organized. It can be hard to find what you want.

###Enter folders

On the desktop, folders have been a useful way to group and label things, so it’s natural to think of them for iOS.

For Weekend Read, a user might have a To Read folder and an Archive folder. Or she might have all the scripts of a certain show in one folder. An actor might keep audition sides separate from other scripts.

On the desktop, you drag-and-drop a file into a folder. Unfortunately, that behavior doesn’t have a great parallel in iOS. Tapping-and-holding on a scrolling list might mean you just want to scroll it.

iA WriteriA Writer pulls it off pretty well, though. Tap-and-hold sucks the icon up from its slot in the list view. You can then drag it to an existing folder, or create a new folder by dropping it on another file. (Much like how app folders are made on the home screen in iOS.) To get a file out of a folder, you drag it to a button where the back arrow would be.

The more common solution you see in iOS is using Select to choose items from the list view, then offering the choice of moving them into a folder (or making a new one). This follows the tradition of Photos, and feels like the Apple Way. GoodReader and Byword both do it this way.

(Sidebar: Like Rene Ritchie, I wish Apple would follow the path of Photos and create [something like Files.app](http://www.imore.com/ios-7-and-my-continued-unrequited-desire-filesapp) to serve as a repository. It would greatly simplify interoperability between Weekend Read and apps that create Fountain files.)

Once you have files in folders, you have to figure out the right way to navigate through them. On the iPhone, we’ve come to accept that tapping on a folder moves you one screen to the right, where we show you the contents of that folder.

For Weekend Read, that mostly makes sense, but we’d have to put a back arrow where we current have the + to add a file. Not awful, but logically it might be nice to hit that plus and mean, *import a file into this folder.*

Further decisions:

* Does deleting a folder delete all the files inside it?
* How do you rename a folder?
* Can you nest folders?

###The Single Folder Solution

At our meeting today, Nima wondered if we could get by with just one folder called Archive. This tracks well with how people use Gmail, and might be enough for many users.

Essentially, everything you see in your Library would be stuff you’re reading now. Stuff in your Archive would be out of sight — still on your phone, but not cluttering your view. That’s not unlike the experience with Kindle, where you can always download something you’ve deleted off the device. It’s organizing by getting rid of things.

From a UI perspective, we’d probably make Archive a choice next to Delete when you swipe right-to-left. (And in the Archive, an equivalent choice would move it back to the Library.)

###Tagging

With folders, a file can only be in one place at a time. A script can be in the To Read folder or the Hannibal folder, but not both.

With tags, that script can be in both categories simultaneously. Evernote and Vesper both use tags extensively, and recent versions of Mac OS have encouraged tagging over folders.

In Weekend Read, we’d presumably allow users to tag files the same way we rename them, by tapping-and-holding on the file. One could also tag by Select-ing a group of files and applying the same tag to all of them.

Once tagged, we’d provide filtered views that only show matching files. (But how? Possibly by tapping on the Library title.)

There’s a lot to love about tagging, but in my heart of hearts, I just don’t see people embracing it. It feels like a power-user feature, and overkill for what we’re trying to do.

###Search

Regardless of which — if any — of these options we choose, one thing we will look at adding is a search field. On both Mac and iOS, I’ve gotten increasingly comfortable with just searching for what I want rather than trying to find it.

As it stands now, I’m leaning towards the one-folder solution, but I’m eager to hear more feedback from users and other folks interested in UI. [Weekend Read](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8) is free in the App Store. You can find me on Twitter [@johnaugust](https://twitter.com/johnaugust).

Opening a script from in Mail in Weekend Read

March 22, 2014 Apps, Weekend Read

One of the most common uses of [Weekend Read](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8) is to open a script someone has emailed you.

Here is the “right” way to do it:

1. Go to Mail.
2. Find the email with the file attached.
3. Tap and hold on the file, then choose “Open in Wknd Read.”

The trouble is, it’s entirely reasonable to go to Weekend Read first. We let you import a file from Dropbox or a clipboard URL. Why don’t we let you import from Mail?

Because we can’t. Apps are sandboxed, and there’s simply no way for Weekend Read to reach into Mail and see what files are there to be imported. ((GoodReader skirts around this by asking for your email login information and checking the mail server itself. That’s more responsibility than I felt comfortable having as an app developer.))

Yet it’s a normal, natural instinct for a user to want Weekend Read to work this way.

So for Weekend Read 1.0.2, I asked Ryan and Nima to add a Mail option that would simply switch the user over to Mail. Basically, “Oh, you want to import a file from Mail? Here, let me take you to Mail.”

But you can’t even do that. Apple provides a URL scheme for creating a new message in Mail, but not to simply switch to the inbox.

iPhone screenshot

Faced with these limitations, we still wanted to make adding a file from Mail as pleasant as possible. I asked Ryan Nelson to come up with a new animation that would show exactly how to add a file. I’m really happy with the result.

Now, whenever the user chooses Email from the list of import options, she is presented with a card acknowledging what she’s trying to do: “It’s easy to import a file from Mail.”

If she clicks on the “Show me how” button, she gets a looping animation that walks her through the process.

It’s entirely possible that a user will forget how to add a file from Mail and click on it again. That’s okay. The experience is consistent and predictable. If you’ve forgotten how to get to a file in Mail, you can learn again in 12 seconds.

Here’s the animation Ryan made:

Screenshots can show you what something looks like; animation can show you how something works.

But they can also be really annoying. When Facebook’s Paper app launched, it was criticized for its intrusive hand-holding. But I think this is a different case. Here, the animation only plays when you specifically ask for it. You want to know how to do it? Okay, let me show you.

If you want to see what the animation looks like in context, [Weekend Read](https://itunes.apple.com/us/app/weekend-read/id502725173?mt=8) is free in the App Store.

ETA: As I was writing this, a new release of Weekend Read (1.0.3) went live in the App Store, which addresses a minor display bug.

« Previous Page
Next Page »

Primary Sidebar

Newsletter

Inneresting Logo A Quote-Unquote Newsletter about Writing
Read Now

Explore

Projects

  • Aladdin (1)
  • Arlo Finch (27)
  • Big Fish (88)
  • Birdigo (2)
  • Charlie (39)
  • Charlie's Angels (16)
  • Chosen (2)
  • Corpse Bride (9)
  • Dead Projects (18)
  • Frankenweenie (10)
  • Go (30)
  • Karateka (4)
  • Monsterpocalypse (3)
  • One Hit Kill (6)
  • Ops (6)
  • Preacher (2)
  • Prince of Persia (13)
  • Shazam (6)
  • Snake People (6)
  • Tarzan (5)
  • The Nines (118)
  • The Remnants (12)
  • The Variant (22)

Apps

  • Bronson (14)
  • FDX Reader (11)
  • Fountain (32)
  • Highland (73)
  • Less IMDb (4)
  • Weekend Read (64)

Recommended Reading

  • First Person (88)
  • Geek Alert (151)
  • WGA (162)
  • Workspace (19)

Screenwriting Q&A

  • Adaptation (66)
  • Directors (90)
  • Education (49)
  • Film Industry (492)
  • Formatting (130)
  • Genres (90)
  • Glossary (6)
  • Pitches (29)
  • Producers (59)
  • Psych 101 (119)
  • Rights and Copyright (96)
  • So-Called Experts (47)
  • Story and Plot (170)
  • Television (165)
  • Treatments (21)
  • Words on the page (238)
  • Writing Process (178)

More screenwriting Q&A at screenwriting.io

© 2025 John August — All Rights Reserved.