- From: Ian Jacobs <ij@w3.org>
- Date: Mon, 3 Dec 2012 09:52:35 -0600
- To: Tobie Langel <tobie@fb.com>
- Cc: "public-coremob-camera@w3.org" <public-coremob-camera@w3.org>
On 3 Dec 2012, at 9:46 AM, Tobie Langel wrote: > On 12/3/12 4:34 PM, "Ian Jacobs" <ij@w3.org> wrote: > >>> >>> A camera app for anything beyond mobile is going to look strange. (Have >>> you ever tired taking a picture with a tablet? It's awkward[1].) >>> >>> I suggest we split-up the work into two applications. >> >> Can we split the work into two functionalities but leave it as one app, >> where the camera functionality is only available if you have a camera? > > That would require making the camera auto sync with the DropBox account, > which is significantly more complex in terms of JS architecture, but which > would also simplify UX. Let me think about it. > >> Can we (also) address the following scenario without Dropbox (E.g., just >> pushing to an HTTP server): >> >> * With my phone I take a photo. >> * The photo is pushed to a server >> * Any clients who have asked to be notified of updates are notified >> * They reload and have the latest photo. > > This requires the development of a dedicated server and auth mechanism and > is already possible using Dropbox. I'm not sure what the benefits are and > I don;t have resources to build this. The beauty is you don't have to! :) I have no objection to people using Dropbox, but I'd love to have an option of using HTTP. We can push photos to w3.org and read them from there as well. We have servers and authentication. If we can say "Save to <url>" that might suffice, and let the server do the rest. (Comments welcome on this, notably from Dom.) > >> That way I can take a photo with my phone and it shows up on the tv >> screen on the wall (after a short delay). > > If that's the use case, you get it for free with dropbox. Good to know. Ian -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Monday, 3 December 2012 15:52:42 UTC