Make WordPress Mobile

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Isaac Keyet 4:48 pm on January 9, 2013 Permalink | Reply
    Tags: weekly dev chat   

    Weekly dev chat summary for Jan 9, 2013

    Agenda

    • WPiOS
    • WPWindowsPhone
    • WPAndroid

    WPiOS

    Version 3.3.1 of the app is awaiting approval and has some important fixes that should help with some of the issues users are seeing. Version 3.4 is almost ready to go, we’re looking at a submit date (early) next week.

    WPWindowsPhone

    Version 1.9 of the app went live yesterday and was announced. There are some issues with editing pages, we’ll issue a bug fix update asap to resolve this but it will be a very minor release (only that fix).

    WPAndroid

    @mrroundhill let the team know that there are enough issues fixed to warrant a WPAndroid app update. It will be a minor release but it has some important fixes and minor enhancements, such as SSL fixes, stats fix, and using the new Holo theme. A beta will be out by Friday this week, most likely the app update will be submitted sometime the following week.

    Next week’s dev chat

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

     
  • daniloercoli 4:57 pm on January 3, 2013 Permalink | Reply
    Tags: windows phone   

    Version 1.9 of WordPress for Windows Phone was submitted for review today!
    It should be live in a week from now.
    A draft of the announcement post is available on the site here: http://windowsphone.wordpress.org/

     
  • Isaac Keyet 4:44 pm on January 2, 2013 Permalink | Reply
    Tags:   

    Weekly dev chat summary for Jan 2, 2013

    Today’s chat log.

    Agenda

    WPWindowsPhone 1.9

    The dev team provided a little heads up for the progress on WPWindowsPhone 1.9: the update is due to be submitted tomorrow (Jan 3). It includes Featured Images, media improvements, crash and bug fixes (see Trac). Announcement post needs to be drafted.

    Mobile Handbook

    We acknowledged that there’s content to be written for the Mobile Handbook. We’ll all review it and discuss leading up to next week’s dev chat. We decided that there’s a need to have a section on Windows Phone development, @daniloercoli and @aerych will tag-team on that. We also said that it’s better to stay ahead of the curve and start writing ASAP. We’ll all start writing within the next few weeks – some of us have already started.

    WPiOS Mockups

    We discussed @karmatosed‘s wireframes briefly, and decided to continue discussing in the comments of the post leading up to next week. We’re also looking forward to some revised/new wireframes and a review of the (iOS) WP app – pain points and revelations.

    Next week’s dev chat

    The next dev chat will be a regular one and we’ll have it on Jan 9, 2013 at 16:00 UTC as usual. Mark your calendar and join us in #wordpress-mobile on Freenode.

     
  • karmatosed 4:24 pm on January 2, 2013 Permalink | Reply  

    Some suggested mobile designs 

    As @isaackeyet mentioned I’m exploring some options.  I’ve started thinking firstly of some specific screens and will move into some flows this coming week.  These are ideas away from what we have now and that was one of the points in doing this – to not be influenced by what we have and just think ‘what if’.

    Sites subscribed to view:

    Screen stages experimental suggestion: (using colour to indicate either types or graduation for pure styling)


    Adding new post wheel interface:

     
    • John Saddington 3:47 pm on January 5, 2013 Permalink | Reply

      these are so neat! well done!

    • Marko Heijnen 5:46 pm on January 8, 2013 Permalink | Reply

      I don’t think the round menu will work. From what I have learned this causing miss hits. Due to the rounding but also that you can’t really make a round button.

      Most of the design from the IOS app I like. I do however think that the selecting site should be different. So a screen with all sites makes sense to have. With doing this the site/CPT menu is nicer to use.

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

    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: http://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 | 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 | 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 | 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 | 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!

  • Isaac Keyet 10:46 am on December 28, 2012 Permalink | Reply
    Tags: ,   

    Dan, Danilo, and Jorge: check out the Handbook schedule posted here. It contains deadlines for parts of the handbook that you’re writing.

    To the furthest extent possible I think we should try and stay ahead of the curve and create basic documents in all categories – should be easy since we’re splitting the work and have immediate peers that we can ping about layout and content.

    I’ll get a draft handbook overview started with placeholder pages – should be a good way to kick this off. Hello 2013!

     
  • Isaac Keyet 5:07 pm on December 26, 2012 Permalink | Reply
    Tags: , wireframes,   

    @karmatosed will create some wireframes of a re-imagined NUX/set up flow for WPiOS over the next few weeks. She’s also added to this p2 so you’ll see her posting here occasionally.

     
  • Isaac Keyet 4:40 pm on December 26, 2012 Permalink | Reply
    Tags:   

    Weekly dev chat summary for Dec 26, 2012

    Since most of the team is away celebrating the holidays today this week’s meeting was a little different. Basically Noel Tock and I discussed a responsive admin instead of going through the usual. A summary of this chat is here, you can also read the chat log.

    We discussed the need for a responsive admin and the different ways we can go about it. In the end we were pretty much in agreement over how we think it should be done, but acknowledged that it’ll most likely be up to the UI team to figure out a plan and decide how we should go about the project. What we suggest though is the following:

    1. Define screen resolutions we want to focus on (and understanding that the UI should be fluid beyond the pre-defined grid)
    2. Wire up general concepts around key elements and their break points (ex admin bar, navigation) and get a discussion going
    3. Start working on any low-hanging fruit that comes out of these discussions – an easy win is a big win since the release cycles are long
    4. Wireframe and discuss individual pages from the top down, starting with the pages that would have the most impact for mobile users (ex Comments list, Posts/Post Editor, Settings pages). Start individual tickets and have teams for each page.

    For instance it would be a huge win to create a working navigation for screens at 480px or less, regardless of the responsiveness of page responsiveness in the admin. [Editor's note: IMO this should definitely be a priority for 3.6 if we had to pick just one thing to make the mobile experience better. Maybe coupled with a collapsable admin bar.]

    We also discussed the need to clean up the markup of the admin. In our mind this project can not be about creating more CSS and more JS to “deal with” small screens, but rather a chance to rethink key elements of the admin and make sure they’re implemented in the best way possible from the ground up – for all screen sizes. This is something that’s been brought up in many other discussions about the responsive admin in the past as well.

    Noel is interested in helping out on the technical side once there’s work to be done.

    Next dev chat

    The next dev chat will be a regular one and we’ll have it on Jan 2, 2013 at 16:00 UTC as usual. Mark your calendar and join us in #wordpress-mobile on Freenode.

     
  • Jane Wells 4:55 pm on December 24, 2012 Permalink | Reply
    Tags:   

    Team Rep Results 

    5 people voted, all of whom say they contribute currently to the mobile apps.

    Isaac is the 1st rep, and Eric is the 2nd. Congrats! The new term starts with the new year, so I’ll be in touch re expectations.

     
  • Eric 6:15 pm on December 19, 2012 Permalink | Reply
    Tags: ,   

    Mobile dev chat summary for Dec 19, 2012 

    We had a brief meeting in iRC today.

    Agenda

    • WPiOS status
    • Windows Phone status
    • Forum and Dev blog migration heads up.
    • Mobile Handbooks

    WPiOS

    The current plan is to submit to Apple on December 28th.  Development is proceeding while we await a few API changes.

    Windows Phone

    Version 1.8.1 was submitted Monday and should be available for download by week’s end.
    Work is proceeding on version 1.9 with an early January target for submitting to the store.  The big items for this release are improvements to the post/page content editor and the addition of featured images.  There are extensive changes in this release so we’ll take some extra time for testing before we submit.

    Forum and dev blog migration heads up

    We mentioned the planned migration of the mobile forums and dev blogs.  @Nacin dropped by to comment that the dev blog migration might begin before the forums and the start date might be the week after next depending on how the holidays go.  The todo list http://make.wordpress.org/mobile/2012/12/19/plan-for-migrating-mobile-dev-blogs-and-forums/ is still valid, just maybe reordered a bit.

    Mobile Handbooks

    We’re not sure what the timeline for having these ready looks ilke or what might be blocking us from starting.  We have a todo of answering these questions.

    Next week

    Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel