Make WordPress Mobile

Updates from January, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • Eric 8:27 pm on January 16, 2013 Permalink |

    Weekly Dev Chat Summary for Jan 16, 2013 

    Chat log (once its available).


    • WPiOS 3.3.1 Released
    • WPiOS 3.4 Status
    • WPWinPhone 1.9.1 Status
    • WPAndroid 2.2.6
    • WPBlackBerry for BBOS10
    • Wireframes and User Test (karmatosed)
    • Handbook Status/Questions

    WPiOS 3.3.1 Released

    WordPress for iOS version 3.3.1 was approved by Apple last week and is available in the App Store. We have seen an early trend of a 50% drop in crash reports with this release! (Go Team!) We noted three major issues remaining are:

    • Draft posts disappearing
    • Issues with logins
    • Issues with media uploads

    We will plan to address these following the release of 3.4.

    WPiOS 3.4 Status

    We’re continue to test version 3.4. There are a few todos remaining but the hope to submit to Apple Thursday.

    WPWinPhone 1.9.1 Status

    Microsoft rejected version 1.9.1 due to an issue with localization. According to their email:

    The application’s UI text is not localized to the targeted language PortugalPortuguese. Instead, it is displayed in English.

    No changes to localizations were made in this release which leads us to think Microsoft changed something in their app review process regarding localizations. We believe specifying a specific localization culture instead of a neutral culture (“pr-PR” instead of “pr”) will satisfy the app review issue. We are submitting the app with this change, but will also reach out to Microsoft directly for any insight they might provide.

    WPAndroid 2.2.6

    @mrroundhill has new version of WPAndroid is beta. Announcements have been made on the dev blog and on twitter. The new version includes the holo theme support for Android devices running a more recent version of the platform, fixes to https and two crashes, and other optimizations. We’ll plan on releasing the app on Google Play Monday. Props to @willnorris for his contributions to this release!

    WPBlackBerry for BBOS10

    @daniloercoli has updated WPAndroid 2.2.6 to be supported on BlackBerry OS 10 when it launches. The new BlackBerry OS will be officially announced January 30th. We will submit the updated app to BlackBerry this coming Friday or Monday so it will be available to BlackBerry users as soon as the new OS and devices are available to the public.

    Wireframes and User Test

    @karmatosed has posted some updated UI examples and also provided a write up of her experience using WPiOS. We skimmed these quickly and decided for @karmatosed and @isaackeyet to talk more in-depth after the dev chat.

    Handbook Status/Questions

    @raggedrobins (irc: siobhan) joined us to field any questions we might have about the handbooks and offered to help out where able.

    @isaackeyet reminded all that the draft mobile handbook is located at https://make.wordpress.org/mobile/handbook/ and of a conversation about the TOC on the blog.  We also have the goal of finalizing the table of contents by January 25th.

    We talked about adding a “Ways to Get Involved” page after the introduction section and a General Guides section before tips and tricks.  We also commented that it would be nice to have screenshots where possible.

    Next week’s dev chat

    The next dev chat will be on Jan 23, 2013 at 16:00 UTC. Mark your calendar and join us in #wordpress-mobile on Freenode.

  • Isaac Keyet 12:38 pm on December 28, 2012 Permalink |

    Got a table of contents ready for the Mobile Handbook – and spent the last few hours thinking about how to best greet new users. Added/rearranged articles and categories as I saw fit but let’s discuss all of this.

    For reference: https://make.wordpress.org/mobile/handbook/

    Also started writing the Design Contribution basics.

    So, thoughts on the ToC? We also need people to write some of the new pages.

    • Dan 3:42 pm on December 28, 2012 Permalink | Log in to Reply

      How about we group the information under each app? Each one would have tools and requirements, tutorials and guides, best practices, references and testing instructions. Otherwise you would have to jump around to find all of the information for one app.

      • Isaac Keyet 4:29 pm on December 30, 2012 Permalink | Log in to Reply

        I like that, but there are also some overarching topics – design, testing, support could all be written independently from the apps.

        Rachel, @raggedrobins: we’ll make these changes for now since they’re only structural. We can switch it around if need be.

    • rachel_mccollin 12:25 pm on January 9, 2013 Permalink | Log in to Reply

      Could the information perhaps be arranged in a modular way, so that the ToC links to overarching topics and to individual apps? Then if a user clicked on the topic, they would see an overview plus the relevant content for each app, and if they clicked on an app they would see an overview (and anything app-specific) plus the relevant topic content for each app. I guess it would mean using tags – I haven’t worked on Docs before so don’t know how straightforward it would be. Shoot me if I’m making things too complicated! 🙂

      • Isaac Keyet 3:39 am on January 10, 2013 Permalink | Log in to Reply

        The theory is that most potential contributors would only be interested in one platform – and since all code bases are different there are different ways you would go about most things (set up, guides, best practices, references, testing). Some over-arching things may make sense to have outside the per-app structure (e.g. API, Design guidelines). That’s my opinion at least. Feel free to elaborate, maybe I misunderstood you!

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar