Return-Path: 
 <dev-return-34340-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-dev-archive@www.apache.org
Delivered-To: apmail-cordova-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6F18E11868
	for <apmail-cordova-dev-archive@www.apache.org>;
 Fri,  6 Jun 2014 20:24:44 +0000 (UTC)
Received: (qmail 22551 invoked by uid 500); 6 Jun 2014 20:24:44 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 22514 invoked by uid 500); 6 Jun 2014 20:24:44 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 22503 invoked by uid 99); 6 Jun 2014 20:24:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2014 20:24:44 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.128.176 as permitted sender)
Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com)
 (209.85.128.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2014 20:24:40 +0000
Received: by mail-ve0-f176.google.com with SMTP id db12so936774veb.35
        for <dev@cordova.apache.org>; Fri, 06 Jun 2014 13:24:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=dm8bNpSzeHSLiP2ckk6lcKfa/bh5l08a1LXPoMD8lPg=;
        b=hWAnqvI7qPWLlJtQCrB0JGMG/DhqzpDIp+qbTfN27Y6RZBznAXftUFFj8OdjeacpDR
         TZENHEQJLqQvmSg4UbgodwDhQ6Vauvuyp0BPLlJNCQ7lWuEDnSiWRa+XwSW3hXbkL3Xy
         pGjpIu2tGzse7y3Js+dw057rxsVWSUizAB+4KsHHVmVK22DVohfYo3WAVCbFDLG7cq07
         SEPC7mndxAXg40Yam7HB53bNMmKtImwdiBIBZvhqXPsH5mBjOzw2zVGNRDeatVYD9S+U
         BNUe4KMmmOOoAnpFayShEKkFYn62PLUNj/2w7LXcf2ExcK8DKgGVfHezJBfLw/QJV2P4
         MoOA==
MIME-Version: 1.0
X-Received: by 10.52.249.76 with SMTP id ys12mr6900412vdc.63.1402086256683;
 Fri, 06 Jun 2014 13:24:16 -0700 (PDT)
Received: by 10.58.197.97 with HTTP; Fri, 6 Jun 2014 13:24:16 -0700 (PDT)
In-Reply-To: 
 <165a2a76328b4a79bd51e37e75efd64d@BL2PR03MB193.namprd03.prod.outlook.com>
References: 
 <165a2a76328b4a79bd51e37e75efd64d@BL2PR03MB193.namprd03.prod.outlook.com>
Date: Fri, 6 Jun 2014 13:24:16 -0700
Message-ID: 
 <CAKP6k2umrhO8rqLCHHzP5UJQ9j7mUtyp6Hh4JN9X4ko-g6-W3A@mail.gmail.com>
Subject: Re: Cordova strategy for Hosted Apps
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e01537eae462f9804fb30a568
X-Virus-Checked: Checked by ClamAV on apache.org

--089e01537eae462f9804fb30a568
Content-Type: text/plain; charset=UTF-8

Hi Jeff,

1. Currently (out of the box) you can load the start page from the network
or the device file system.  However, you need to be aware of both CORS
issues as well as App store policies which may make this approach
un-submittable [1] . You can achieve this either by setting the <content
src=''/> in your config.xml file, or by redirecting from the index.html
that is packaged with your app.  The latter approach allows you to respond
to no-network issues, which you must do in mobile anyway.  cordova.js will
need to live with your server pages, and any plugins, and
cordova_plugins.js and all plugin files must match the versions of the
native implementation that is compiled in the app.

2. Yes, it is a great way of testing, as you can skip the whole build, and
just reload. If the app should function with/without the feature, then yes,
it should detect it.

3. Similar to what you describe in  #2, for targeting browsers generically.

[1]
2.12 Apps that are not very useful, unique, are simply web sites bundled as
Apps, or do not provide any lasting entertainment value may be rejected.
https://developer.apple.com/appstore/resources/approval/guidelines.html

Cheers,
  Jesse


@purplecabbage
risingj.com


On Fri, Jun 6, 2014 at 1:02 PM, Jeff Burtoft <jeffburt@microsoft.com> wrote:

> I have a tool that allows developers to take their web apps and build them
> into hosted store apps on Windows 8.1 and Windows Phone (8 and 8.1) called
> the Web App Template<https://wat.codeplex.com/>.  Some of the developers
> who are using the tool would like to see it go cross platform to Android
> and iOS, so that the same config file could be used to build hosted apps
> for the play store and App store just as it is on Windows.
> I love the idea of going cross platform, and when I think cross platform,
> I think Cordova, but after looking through some of the documentation, I'm
> not sure if it's a good fit.  I'm looking for some direction on these
> questions:
>
> 1.       Does Cordova have "hosted apps" (where the content lives on the
> server as opposed to being packaged with the app) in its roadmap?  I
> realize you can do this today on most platforms with a redirect, but it
> seems to be more of a work around rather than a strategy.
>
> 2.       Does it make sense to make Cordova device APIs available to
> hosted apps?  In general these apps also must function in a browser , so
> the features would have to be implemented in a progressive enhancement
> model.
>
> 3.       I see a build for Browser<
> https://github.com/apache/cordova-browser> on the Cordova website.  What
> are the plans for this build?
>
>
> Can anyone help clarify some of this?
>
> Thanks,
> Jeff Burtoft
> --------
> HTML5 Evangelist \\ Web Technologies
> \\ Microsoft
> --------
>
>

--089e01537eae462f9804fb30a568--