It is exciting to see that there is
community interest in a mobile skin for RC. As it so happens I am
on contract with a large American retailer with a Kolab Server
based groupware environment, and my current project is developing
a mobile skin for RC that will be used in house, but will also be
released as an open source project once we have it production
ready. Our approach is to create a UX that is much like a native
mobile app, and not just a smaller, scaled down "Larry" or
something like that. In fact our goal has been to refactor the
whole client side (as much as is necessary at least) of RC from a
mobile first perspective, and stay as far away from looking, and
feeling like Larry as possible. Note that there are NO changes to
the RC code base. Everything is accomplished within the scope of
the skin.
We have a requirement to support "all" possible mobile devices (At
what point does that request become unreasonable?), because with a
couple of hundred thousand users all owning different devices we
cannot realistically limit what the users would be "required" to
use in order to functionally use the application, nor can we
predict what they are using now, or will be in the future.
Besides, for it to be truly useful to the RC community at large
the skin must be as platform independent as possible.
On 4/15/13 10:58 AM, Kelsey Cummings wrote:
On Mon, Apr 15, 2013 at 01:50:28PM +0200, Thomas Bruederli wrote:
...
happen. We'd really appreciate your work on this. But please consider
to more focus on a responsive skin that scales for a variety of
devices from desktop / tablets down to mobile phones. A pure mobile
skin isn't the most sustainable solution for today's needs.
We have a lot of interest in this. It is clear that a lot of users
access their mail via webmail on their tablets. We all know that
they'd be better served using the native app but there are cases where
this may not be an option. We'd be happy to sponsor this. We're going
to see what we can do to make the larry template at least function on an
ipad - I don't have the details but apparently there are issues which
renders it "unusable."
--
