WordPress for iOS
Isaac Keyet (isaackeyet)
Eric Johnson (aerych)
Dev chat summary for April 24, 2013
Agenda
- iOS : version 3.5.3 released
- iOS : status
- Android : version 2.3.1 released
- Android : status
- Windows Phone : status
- Mobile Handbook Reminder
iOS : version 3.5.3 released
The latest version of the app was released on Monday April 23, and has fixed even more crashes and bugs. Unfortunately there’s still a crash occurring with featured images.
iOS : status
Now working on some improvements to the WPcom Notifications screen and looking into ways the app can better handle accounts (from both WPcom and multisite installs).
NUX project: wrapped up (*crosses fingers*) some of the stuff that will improve the signup flow and have shifted toward the wizard walkthrough features.
Native WPcom reader project: implementation is progressing. Basic views are implemented and being iterated on. Currently working on the best way to handle video in posts.
Android : version 2.3.1 released
A bug fix update for version 2.3 (Holo update) of the Android app was released. This took care of a handful of crashes and a multitasking issue.
Android : status
Another bug fix release with some fixes to the ActionBarSherlock library and James Hu’s comment editing patch.
The next major version is 2.4 (WPcom Notifications). This release is progressing, push notifications are working and the UI is being wired up.
Windows Phone : status
Nothing big in the pipeline, although there’s now a milestone with tickets for the next update.
Mobile Handbook Reminder
There are quite a few items left to do, both assigned and open — you know who you are! Let’s wrap this up. Eric said he’s started to look into the remaining items for Windows Phone.
Rachel got in touch (yay!) so we’ll bring her up to speed on the status of the handbook as well.
Next week
The next dev chat will be on July 1, 2013 at 1500 UTC. Mark your calendar and join us in #wordpress-mobile on Freenode.
Hi there, I’ve put together a spreadsheet here: https://docs.google.com/spreadsheet/ccc?key=0AiTZlIvtDmPEdDQxQkV6bGdTN3VWWHVhYlpEU0NENWc
You’ll see the main sections, and you can insert a line underneath the sections for the individual document title. Use – to show a hierarchy. I’ve added some content so you can see what I mean.
I suggest using the following workflow:
1. Create the table of contents.
Add all of the titles of the individual articles you need. Move the rows around to create the table of contents. This means you’ll have a complete list of things that need to be written when you get started.
2. Start Writing
Author puts their name in the Author column, creates page and adds a link. Change the status to In Progress. When you’re done change Status to Needs Editor. It’ll be looked at by an editor. When they’re happy they’ll assign a proofreader. When the proofreader is done they’ll mark it as complete.
Comments can be added to the comments section – this could be on issues you’ve got, or suggestions from the editor.
Where will be build it?
There are a few options:
1. Build it on make.wordpress.org/events/handbook
2. Create another site and then migrate it when we’re done.
I was naturally thinking about building it on events/handbook/ but it could actually be good to set up a site and build it on there. That way we can use something like Edit Flow for comments, create tags and custom statuses, and have a bit more control. Then when the content is done we could migrate it to make.wordpress.org/events/handbook
I don’t mind either way though, and would appreciate any input or thoughts you guys have on it.