Archive

Archive for the ‘iPhone’ Category

iPhone Badge API

July 15th, 2010 No comments

The iPhone is in desperate need of an API that will allow a developer to post a count, such as that used on the icon badge and an optional short message.

A developer can then use the information posted by any application in a single application that will display the counts, the optional message and allow the user to launch the application that generated the data.

Please create a unified API that developers can use to post messages to, such as the total count used on a badge. The purpose is to allow any developer to create an application that can read the common values posted here and use them to display these counts in another program.

For example, I have a dozen or more programs that update their badge count when an event happens, such as a facebook update, or new mail is received in Mail. A developer could write a program that would take all the badge counts, along with maybe a short message, and display them to the user in a single application. The API should also allow the user to be able to launch the program that generated that badge count.

Categories: Development, iPhone Tags:

The App Store unofficially breaks 100,000 approved apps

October 27th, 2009 No comments

The App Store unofficially breaks 100,000 approved apps

It’s another milestone (unofficially) met, as Apple has passed the 100,000 threshold of approved apps in the App Store, according to App Shopper. If you’re unfamiliar with App Shopper, they list all of the apps that are in the store, tracking updates and price changes. As of this writing, they’re listing 101,847 apps approved for sale and 93,118 actually available. We imagine Apple will make an announcement when the latter number officially hits 100,000.



Just last month, Apple announced that there were upwards of 85,000 apps available for purchase with sales figures in the billions — 2 billion apps sold in fact, though there’s no word on the mix of paid vs. free.



Despite the (often significant) bumps in the road, the App Store continues to grow at an incredible pace.
www.tuaw.com

Categories: iPhone Tags:

iAltair

October 23rd, 2009 No comments

The Altair 8800 from MITS of Albuquerque, NM, was my first computer. It came as a kit and was initially called a “minicomputer” in 1975. It had 256 BYTES of memory, which would not be enough to store this review. The front panel (the icon has the 8080B) had 2 rows of switches and 2 rows of LED’s. In simple terms the top row of switches controlled the address and data registers (memory) and the buttom the cpu (run, single step, input/output, write/read, etc).

After building the 8080, there was no operating system, no basic, no nothing. You would create your very simple “program” by flipping those switches and hoping to get a reaction, such as adding some binary numbers together. Eventually BASIC would become available along with 1k memory board. I had hooked this up to an ASR33 teletype machine and was able to finaly save and load programs using paper tape punched with holes.

It would be another year before a floppy was added, and you had to write your own assembler programs to make them work. When Gary Kidall released CP/M, it still required a lot of hours to get it to work and you had to “roll your own” BIOS (Basic Input / Output System) or “drivers” to get anything to work.

The first Apple computer would become available about a year and half later and also came in a kit. But it had BASIC built in and only had to be hooked up to a TV screen to make it work.

Interacting with CP/M was done on a paper printing terminal rather then “glass” dispaly. Eventually I got an ADM display.

When I first saw this I was hoping for a real simulator with functioning switches and controls, but, alas (as Jerry Pournellle would often say) it accomplished its goal of taking me down memory lane.

However, this is part of the Computer History Simulation Project.

Apple AppStore Link

200910240158.jpg

The Altair 8800b model.
200910240159.jpg

Categories: iPhone, Reviews Tags:

2Do

October 18th, 2009 No comments

2Do is a visually stunning todo manager with a user interface that is well thought out. As with Guided Ways Groups application, I like the (optional) side tabs, allowing one to quickly jump to group of tasks without having to navigate through an extra set of menus or screens.

The task detail screen is clean and easy to read. One can also assign multiple alarms to a task.

While all the basic info one needs is in the tasks there are some additional fields that I’d like to see in future versions. One is the ability to attach contact(s) to a task, so that I can quickly call or send an email to that person. Another is the ability to attach location data / map to a task, a feature that is becoming common in iPhone apps everywhere. Because the layout of the detail records is nice an clean, adding additional fields should be a fairly easy proposition.

2Do should also incorporate support for urls (and url parsing) in its notes fields, which it currently doesn’t do.

A companion desktop app for OSX (free) allows the syncing of tasks to iCal, which has always been one of my criteria for calendar or tasks programs in the past.

2Do can be found at the iTunes store here.

2Do-Site-Overview.jpg

Categories: iPhone, Reviews Tags:

Frustrations with SpringBoard

October 16th, 2009 No comments

I’m frustrated with the limitations imposed on my use of apps on the iPhone.

The entire model for organizing the apps that I have purchased is severely restrictive and counter-intuitive, actually, rather non-Apple from a UiX perspective.

First and foremost is the limitation on the number of installed apps. There is simply not enough room to display the apps that I actually use as well as those that are more occasional/transient, such as games or books.

While the new iTunes interface is a help towards the management of the apps, it doesn’t provide better models for managing groups of apps.

For example, the option to sort by date purchased should be added. There should also have a means to save an entire page of apps and replace it with another, assuming that we are going to be stuck with the current limitation on the number of installed apps that are visible.

Second, the interface itself should allow the user to configure pages of apps by their own category.

If I can setup a group called “Network Utilities”, that has 20 apps, I should be show 2 pages for that group with the corresponding apps.

There should also be a mechanism to quickly jump from the “home” page to any of the application groups that have been defined, such as double tapping the hope button brings up an “Expose” style display of all the groups.

Another sore point in the user experience is the lack of a “recents” apps. When you have 200 apps installed, some only accessible via Spotlight, and you get a call, its a royal pain in the arse to have to locate the app one was just using.

Why can’t the user simply tap the recents and have a “coverflow” style display of apps that they used?

Perhaps a solution would be to open up the SpringBoard API to developers and allow the developers to create new and novel ways to navigate and launch apps they are using on the iPhone and/or iPod Touch.

This would be an ideal solution to the management of apps on the iPhone.

Updated with the following found videos:

Expose


Coverflow


Categories: iPhone Tags:

AT&T Failures Part 2

October 11th, 2009 No comments

Each day that passes the percentage of call failures we have in my neighborhood in downtown Manhattan gets worse. I’ve been using a free program called Signals by Sudobility (who are responsible for several excellent iPhone apps, including Night Camera). Unfortunately, the latest release of Signals had a bug and is currently waiting for “re-approval” by Apple (a topic worthy of another post).

AT&T really needs to step up to the plate on this and issue credits. I’m sure that many people are in the same situation that I’m in and we are not receiving the level of service that we are currently paying for.

IMG_1657.PNG

Categories: iPhone Tags:

AT&T NYC Plans

September 25th, 2009 1 comment

Because of AT&T failures to provide adequate iPhone service in NYC, I can’t continue to recommend the iPhone for most users until the network issues are addressed. This unfortunate state is solely AT&T fault and they are acutely aware of this.

One could say AT&T is guilty of Fraud, Misrepresentation, Interference with Business Relations, Deception and Unjust Enrichment, just to name a few causes of action. I believe that AT&T should issue a credit to iPhone users, such as a free month of service to compensate for their failures.

9 out of every 10 calls I make or receive are dropped. Despite having “5 bars” there are times my iPhone will not ring. Callers sometimes do not even get my voice mail and instead are told that I have refused to accept their call, or that I have not enabled my voice mail. There are times when voice mail is not delivered for hours or even days.

Today, my phone shows 5 Bars and no 3G and I can not make or receive calls.

I called AT&T Customer Service to complain and after a few “passing the buck” phone transfers I was very surprised to find myself speaking to a high level AT&T executive on the issue of the iPhone in NYC. We spoke for about 30 minutes.

While he did not mention that any of the information shared with me was confidential, I do not wish to identify this person at this time (just in case). Let’s just say that its a name I’ve heard before.

Here is some interesting information that was disclosed to me during the call.

AT&T is acutely aware of the network issues they are having, in particular with iPhone users.

Some of the problems are not the cell towers themselves but the backend end. The switches, routers and fiber infrastructure is operating at (and sometimes) over capacity. This explains why one can have 5 bars of service and get “Called Failed” messages.

AT&T is (finally) installing “picocells” in NYC and other cities. Picocells are used extensively in Europe and Asia and are tiny little cell transmitters (often about a square foot in size and flat) attached to the side of a building or a lamp post rather then the much larger cell antennas that are on the roof tops of buildings. Picocells handle fewer calls but put one on every block and coverage increases exponentially. Another benefit is that picocells reduce the power needed by a cell phone radio since the signal is much closer to the phone.

US Carriers have often resisted the use of picocells since they increase number of units requiring maintenance and service but are known to install picocells inside corporate office buildings.

I had an employer once who used Sprint for the 300 or so corporate cell phones and Blackberry’s. We had virtually no Sprint service in the office building and Sprint installed a couple of picocells on the floor. Suddenly everyone had great cell service, even in the stairwells.

Picocells are similar to the home based “Microcell” product that AT&T is rolling out for home users (which plugs into your internet connection).

AT&T is also converting and/or adding cell sites to operate at 850 Mhz rather then 1900 Mhz. Why is this good? Lower frequency signals travel through buildings much better then high frequency signals. This means that more phones will be “line of sight” with a cell tower despite having a building blocking the visual line of sight. It also means that people in office buildings will have better signal strength inside the building and penetration underground (e.g. subway stations) will also improve.

During the call, I pointed out that the network is often overloaded when special events take place, such as Fashion Week or the UN General Assembly. These events concentrate thousands of users in a small area completely overpowering any existing infrastructure. Anyone at Fashion Week in NYC last week knows how difficult it was to make or receive any calls in the vicinity of Bryant Park.

My suggestion was simple. Keep track of the events taking place in this cities and bring out mobile cell trucks to handle the overload.

This was proven at this summer’s SXSW conference in Austin, TX, when thousands of iPhone users showed up and could not use their phones. The following day AT&T rolled out some portable cell towers and alleviated the congestion.

They can mitigate many complaints and improve the service at the same time.

I also suggested they provide an application such as “Signals” (iTunes Link) and allow the users to report back signal strength. They can benefit from the crowd sourcing of data collection to improve the service. The iPhone 3GS with its built in GPS can provide pretty accurate location data which combined with signal strength can really go a long way to improving the quality of service.

So AT&T – hurry up with the improvements and consider what you can do for those iPhone users who have suffered for your lack of preparation and planning with your network.


Categories: iPhone Tags: ,

iPhone needs a common file storage & transfer API

September 14th, 2009 No comments

The iPhone API has one very big and very non Apple (e.g. inconsistent and unintuitive) behavior due to the lack of a common file storage API. Any application that will allow the user to access its files lacks any consistent method to transfer files and to share files.

This lack of a thought out API for files (other then an applications own files) and for any form of file transfer as resulted in the mess iPhone users find themselves in today. Applications might use a desktop client, or they might use a web server or an ftp server, all extra code that is completely different from one application to another.

The iPhone really needs a common file system, like the Newton’s “Soup”, that allows applications to access this common storage area that can be separate from the rest of the OS file system.

Because each application is “sandboxed” it can only view and act on its own files and on photos. The user should be able to transfer a file, say a PDF or a JPG, and any program that can read / write the file should be able to have access to it.

A common file system will also eliminate another problem, the potential loss of data when a user updates an application or has to delete it and then reinstall it.

The File System API should allow:

  • Bidirectional file transfers via iTunes (or other)
  • Allow files to be private to a specific program
  • Allow files to be available to any program
  • Backup separately from the rest of the iPhone backup process

Categories: iPhone Tags: