Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of shazron@gmail.com designates
 209.85.128.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOBL_k4phUT5mk8YZRSnYcHYP=FgsWnHHwS_62+4gJYdT4v32g@mail.gmail.com>
References: 
 <CAOBL_k4phUT5mk8YZRSnYcHYP=FgsWnHHwS_62+4gJYdT4v32g@mail.gmail.com>
From: Shazron <shazron@gmail.com>
Date: Mon, 20 Jan 2014 10:47:19 -0800
Message-ID: 
 <CAE6O_-b7e55-PTw9Ww9xX3CyFBB+oKnJ=MSxQDH1W7514J_O8A@mail.gmail.com>
Subject: Re: [Android] InAppBrowser sucks and needs a re-write
To: "dev@cordova.apache.org" <dev@cordova.apache.org>,
 "bowserj@apache.org" <bowserj@apache.org>
Content-Type: multipart/alternative; boundary=001a1133f0b8a4e7bd04f06b54b0

--001a1133f0b8a4e7bd04f06b54b0
Content-Type: text/plain; charset=ISO-8859-1

I know this is an Android thread, but speaking for iOS: -1 for shitcanning
it cross platform.

Our users still care I believe... it is important for some web OAuth
authentication etc (FB, Twitter) but not sure if its as important on
Android like iOS (perhaps the workflow is different).


On Mon, Jan 20, 2014 at 10:37 AM, Joe Bowser <bowserj@gmail.com> wrote:

> Hey
>
> So, after spending a bit of time with InAppBrowser, I think we should
> get rid of it.  It serves almost no purpose, and it's way too complex
> of a plugin for us to maintain.  However, nobody would agree with me
> about shitcanning this thing, so instead I propose we re-write the
> whole thing because it pretty much needs to be green-fielded.
>
> Part of the reason is the fact that the UI is all hardcoded when it
> doesn't need to be.  Now that we're moving around resources, we should
> be able to move around XML layouts and use this instead of hardcoding
> our UI in JS.
>
> The other part of the reason is that I think that too many new
> features got added to InAppBrowser, and I don't think anyone actually
> knows how this thing is supposed to work.  Furthermore, I think that
> on Android, even if you follow Android guidelines, the InAppBrowser
> looks totally stupid and it screams "This is a PhoneGap App therefore
> it sucks!".  If our users can tell if an app is written in Cordova, we
> have failed.
>
> Now, I'm fine with moving out the UI, but I want to know how much
> people care about this stupid plugin.
>
> Also, on another note, has anyone tried starting Chrome with
> startActvitiyForResult and onActivityResult? I'd much rather have
> chrome appear and have Chrome pass the results back than our stupid
> half-baked browser.
>
> I'm sure everyone has thoughts on this, so let's hear them.
>
> Joe
>

--001a1133f0b8a4e7bd04f06b54b0--