My main thought is "if you're building an Android app, follow the current (Marshmallow) Android design guide". That way things work as people expect, plus, by now it's generally quite good advice anyway, I think.
But I guess youvre wanting to take a step back now, and not think it terms of visual design but simply the flow of using the app. I don’t really feel there's much to comment on at the moment - perhaps if you have ideas a flowchart and /or sketches might help? - but one thought re compose: I believe that there's an intention for DW to support draft and scheduled posts, so that should be probably be allowed for (even if not used) from the start,even if not exposed in the UI. Possibly the infrastructure for offline sync relates to that nicely, possibly not...
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2016-01-21 11:30 pm (UTC)But I guess youvre wanting to take a step back now, and not think it terms of visual design but simply the flow of using the app. I don’t really feel there's much to comment on at the moment - perhaps if you have ideas a flowchart and /or sketches might help? - but one thought re compose: I believe that there's an intention for DW to support draft and scheduled posts, so that should be probably be allowed for (even if not used) from the start,even if not exposed in the UI. Possibly the infrastructure for offline sync relates to that nicely, possibly not...