Re: [85attendees] IPhone app for ietf

Tom Pusateri <pusateri@bangj.com> Wed, 07 November 2012 21:14 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: 85attendees@ietfa.amsl.com
Delivered-To: 85attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1293521F8BE7 for <85attendees@ietfa.amsl.com>; Wed, 7 Nov 2012 13:14:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.724
X-Spam-Level:
X-Spam-Status: No, score=-1.724 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unNuVnBmsY2T for <85attendees@ietfa.amsl.com>; Wed, 7 Nov 2012 13:14:35 -0800 (PST)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) by ietfa.amsl.com (Postfix) with ESMTP id 896BD21F8B16 for <85attendees@ietf.org>; Wed, 7 Nov 2012 13:14:35 -0800 (PST)
Received: from dhcp-5493.meeting.ietf.org (dhcp-5493.meeting.ietf.org [130.129.84.147]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 5E08211B9A; Wed, 7 Nov 2012 16:12:12 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tom Pusateri <pusateri@bangj.com>
In-Reply-To: <p0624060bccc075d1cf1f@dhcp-4049.meeting.ietf.org>
Date: Wed, 07 Nov 2012 16:14:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E73C856-377D-40BB-A306-6AB493B73313@bangj.com>
References: <2910961148818266601@unknownmsgid> <CAA=duU258jeA0nN9hWVAYRyELd=PGLq8gMeYEM6ZCOxtcaKdyA@mail.gmail.com> <p06240608ccc06ed02ab1@dhcp-4049.meeting.ietf.org> <BF55E385-F420-4F6E-8942-1E62A876A3FB@bangj.com> <p0624060bccc075d1cf1f@dhcp-4049.meeting.ietf.org>
To: Randall Gellens <randy@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1499)
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "85attendees@ietf.org" <85attendees@ietf.org>, "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: [85attendees] IPhone app for ietf
X-BeenThere: 85attendees@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF 85 attendees mailing list <85attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/85attendees>, <mailto:85attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/85attendees>
List-Post: <mailto:85attendees@ietf.org>
List-Help: <mailto:85attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/85attendees>, <mailto:85attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 21:14:36 -0000

On Nov 7, 2012, at 3:33 PM, Randall Gellens <randy@qti.qualcomm.com> wrote:

> At 3:17 PM -0500 11/7/12, Tom Pusateri wrote:
> 
>> On Nov 7, 2012, at 3:03 PM, Randall Gellens <randy@qti.qualcomm.com> wrote:
>> 
>>> At 7:15 AM -0500 11/5/12, Andrew G. Malis wrote:
>>> 
>>>> Make sure you have the most recent version from iTunes. It should be version 1.5 (you can see the version in the Settings app).
>>> 
>>> Sadly, 1.5 requires iOS 4.3 which is not available for an iPhone 3G (I know, time to upgrade).
>>> 
>> 
>> Yep, it pained me to drop iOS 4.2 support but the SDK required it. I couldn't have both native iPhone 5 support for the new larger screen and iOS 4.2 support for the iPhone 3G so I chose the iPhone 5.
> 
> I understand.  Well, that just clinches it: I need to upgrade (I've been reluctant because I need to pay full price).
> 
> I'm curious why an update is needed to get information on new meetings?


The app gets updated in the app store to include new maps, room numbers, Working Groups, BOFs, etc. typically once per meeting. The formats of the schedule sometimes change and it's really best if I can test it with the new agenda each meeting to find any unexpected crashes due to data format changes.

This was expedient for releasing the app but long term, this info could be downloaded on the fly. It is just a matter of defining a RESTful interface to the data, hosting it somewhere, and updating the app to pull it in.

Based on my schedule, I can do this but it hasn't been high priority. I would rather add new features.

Tom