Mobile web/Etherpad/2013-10-9-Preparing for VE on Mobile
Appearance
10/9/13 preparing for ve on mobile Attending: Kenan, Tomasz, Rob M, Juliusz, Arthur
How to structure spikes on VE for mobile?
[edit]- section-level editing
- ux-related issues on tablets
From rob's perspective, main challenges:
[edit]- addressing dependencies on VE/MW core libraries; will likely need to abstract things out
- 'targets' for using VE in different environments (eg for Flow)
- Example: MobileFrontend does not currently have mwuser, will we need to enable this? RL limitations/dependencies
- Need to create MobileFrontend-specific target
- Needs refactoring
- what does it all entail? unclear at the moment
- 'targets' for using VE in different environments (eg for Flow)
Questions that need to be answered (in rough priority order):
[edit]- what dependencies are there right now? (eg might be more than mw.user)
- how do we work around the dependencies now?
- do dependencies have to be loaded on every page view or dynamically?
- Are we going to support section-level editing? sanity check with parsoid team (product q, discuss with parsoid team)
- Are we sure that section editing on tablets is the only answer (how about full page editing w/ section toggling)?
- performance impacts of loading all these modules, what impact is this going to have on mobile pageviews, etc?
- what can we trim out to improve performance? (eg can we strip out rangy?)
- does VE load too slowly (too many dependencies) on tablets or work too slowly (UI too slow)?
- Minerva/SkinMobile
- can we eliminate a need for fragmenting the cache?
- Minerva's UI, especially left nav with all the desktop menu options
- UX on tablets
- intermittent connectivity - error handling
- Product: Subsection editing/viewing on tablets
- Product: Wikitext editing on Tablets
- Product: Anonymous editing
- not necessarily an urgent question that needs answering, but will be helpful in guiding how we architect this
Actions
[edit]- Juliusz/Rob going to carve out time for Juliusz to do engineering onboarding for Rob (to go over our architecture, infrastructure, code base, alpha/beta, etc)
- Rob to speak with parsoid team in regards to requirements ND PROCESS / Timeline
- Kenan needs to answer product quetsions wrt subsection editing, UX, and wikitext editing