Add all official PhoneGap plugins to the PhoneGap app.

This will allow the app to always build with the native chunks of each plugin.

On my home network, hitting a new port for the first time can sometimes take a moment. I'm finding that the timeout period is too short.

Successfully build the WP8 platform.

Version control the platforms/wp8 directory. Add the build artifacts to .gitignore.

Once in a while, an error occurs while connecting to a server that we know exists.

Currently: an error is reported but not details are displayed.

I can't quite find the steps to reproduce this problem, but sometimes when I'm browsing my test www/ I find that in this error gets thrown in the remote web inspector:

ReferenceError: Can't find variable: LocalFileSystem

Referencing this from the homepage.js

    function readFile(filepath, callback) {
        window.requestFileSystem(
            LocalFileSystem.PERSISTENT,
    ...

Once this error gets thrown, the JavaScript stops execution and I'm unable to use the three finger tap to go back to the homepage.

The best way I found to reproduce is to navigate to a page, minimise the app, maximise the app, and then navigate to another page. More often than not, the new page will throw the error but not every time.

eom

The app is designed to fit the device's screen.

For a better experience, we can disable the webview bounce and scroll on iOS.

Successfully build the iOS platform.

Version control the platforms/ios directory. Add the build artifacts to .gitignore.

Ensure that Android can pull the content down without any issues.

In order to serve an app properly, the server component will need to send the correct platform cordova.js. However, since user agent sniffing on the server side can be messy, annoying, and brittle, we'll need to have a way for the app to send a signal telling the server what platform its deployed on.

iOS device

Currently, the visor color is red during the loading state. This is actually used as the alert state for error messages.

While the application is initializing, we should use a more positive state color such as blue (default visor color) or green (implying a success state).

I think blue best represents the loading state, because it is neither a success or error.

During development, especially when AutoReload is enabled, it is frustrating to have the screen lock.

We can add a small plugin to prevent the screen from turning off. However, without a valid reason, Apple has been known to reject app submissions.

The app should gracefully handle address formatting:

• 10.0.0.1:3000 => http://10.0.0.1:3000
• http://10.0.0.1:3000 => http://10.0.0.1:3000
• https://10.0.0.1:3000 => https://10.0.0.1:3000
• example.com:3000 => http://example.com:3000

The plugin should use native code to:

• on volume down, navigate back to the homepage
• on volume up, refresh the connected app

Ultimately, we will need to use a separate CordovaWebView to run the connected app. This will create a sandbox so that the development app cannot interfere with the PhoneGap app's source code. However, talking with Jesse and Joe, the CordovaWebView will not be trivial. So, let's start with something easier to get our feet wet and create something usable.

Ensure that iOS can pull the content down without any issues.

At the moment, the config.xml is locked to 127.0.0.1*.

Now that we've deployed the app to a device, we need to open this to any address and any port.

Remove the need for the user to enter http:// in the IP field - it is implied.

After some usage of the app show a popup that asks if the users likes the app (y/n) and if they choose yes then ask if they want to submit a review in the app store.

On my Galaxy Nexus, the events fires one-in-ten taps.

I can't figure out what causes it to trigger once in a while.

After entering the IP address, the user should press a submit button.

The application view should then change to the remote app (web page).

Create a valid PhoneGap project with at least one platform added.

on about page

http://www.adobe.com/ca/privacy.html
http://www.adobe.com/misc/terms.html

Joni needs to design for all platforms.

On my iPhone 5, I see a flicker when hiding the splash screen and showing the app. It only happens once-in-a-while. I imagine on slower devices, it will be more noticeable.

Ensure that WP8 can pull the content down without any issues.

When the application opens, it should allow the user to enter an IP address. If you think a port should be customizable, then provide that input as well.

We should get in the habit of versioning the PhoneGap App.

I'll tag this milestone as 0.0.1. Let's use the www/config.xml version element to track it.

Opening Application

Should prompt the user for an IP address and port. The port should default to 3000.

Submitting IP Adress

Should simply change the windows location: window.location = location;

It's crude, simple, and nearly useless but it's the beginning of something much better.

@davejohnson you mentioned wanting to add some usage analytics to the app. The submission process is looking slower than expected, so we may have time to add this.

What are you thinking exactly?

The JavaScript is largely untouched since @yoheishimomae initial design. At the very least, we should wrap everything up into a closure. Ideally, we'd like to showcase best practices with browserify et al.

Successfully build the Android platform.

Version control the platforms/android directory. Add the build artifacts to .gitignore.

When selecting the address input field, the selection cursor is not correctly position and the user cannot type. To solve it, the user must select the input field again.

This might be a CSS animation bug.

Using the PhoneGap CLI, the following error is throw:

Cannot read property 'currentVersion' of null

Perhaps the latest cordova-cli is compatible?

Is it possible? How?

Issue #21 deals with how to invoke the reload and back to home functionality.

This issue deals with the implementation of both the reload and back to home.

Back to home is tricky. Our homepage app is bundled at www/index.html. However, we connect to a streaming app at an arbitrary IP address. Essentially, these are two different web sites hosted on different domains.

We need a way to go back to the bundled index.html.

Options:

1. Use the history.back(history.length); approach.

   • The downside is that it displays the cached page. This introduces rendering quirks that we would need to work around

2. Use the FileWriter to write a bundled-app.json that stores settings such as:

   {
       'documentURI': 'file://whatever/long/url/this/is/www/index.html',
       'address': '127.0.0.1:3000'
   }
   

for all platforms. joni needs to put this together.

Scenario: First Application

1. Install the PhoneGap command-line tool from npm:

   $ sudo npm install -g phonegap
   

2. Create a PhoneGap project:

   $ phonegap create my-first-app
   $ cd my-first-app/
   

3. Connect to the PhoneGap App:

   $ phonegap app
   [phonegap] Open the PhoneGap app on your device
   [phonegap] Select “Local Development”
   [phonegap] Address: 192.168.0.10
   [phonegap] Port: 8080
   

4. Open the PhoneGap app.

5. Select Local Development and enter address and port.

6. This displays the application served from your local computer.

7. As files change locally, the PhoneGap App can be refreshed.

So after talking to the legal guy yesterday, he made a really good suggestion about making some really easy to follow guides on how to install the desktop component of the phonegap-app and how to pair to the device. The reasoning for this is so that the app reviewer can review these docs and understand how the whole experience is supposed to work and thus make the review process easier.

This is something we will probably end up doing anyways for app.phonegap.com. If the site is ready before submission, we could probably just send that as that the tutorial.

We store a few configuration settings:

• server address
  • it's a pain in the ass typing an IP over-and-over
  • often developers are connecting to the same server
• application's bundled index.html URL
  • needed to go to the home page from the streamed app
  • cannot used window.history.back(window.history.length);
    • going back in history will display the cached page state
    • we can reset this state, but it's opening new issues
    • a remote reliable approach is to navigate forward to the www/index.html

Once we have connected to the streamed app, we are essentially viewing a different domain and different web site. We cannot access localStorage or sessionStorage. The only common place of storage is the file system.

It gets stuck on the loading screen.

We want to switch from the currently implemented design (showing Login and Password fields) to a single field for IP address.

Display the URL-specific keyboard instead of the generic keyboard.

Also ensure that autocorrect and autocapitalization are disabled.

When the notification bar is enabled (e.g. hot spot is turned on), the splash screen will jump vertically when transitioning to the app.

Add Tim, Herm, and Michael to the profile.

Let's use the awesome UI skin that Yohizzle created (in the res/design folder).

Replace with what is being used right now (the PG getting started skin).

The tap-information labels should not be selectable.

So that we can easily install the latest release.