Category: Applications

The Apple Maps Fiasco Finally Hits Me – Tiffin St, Not Giffin St

Until last night I had been blissfully unaffected by the whole Apple Maps fiasco. I upgraded both my iPhone and iPad to iOS 6.0 and have generally had no problems whatsoever. I've gotten to where I needed to go when using "Maps" and in fact I like the better driving directions.

And then last night I read an article in our local paper about a building to be demolished and wondered where that was in Keene, as I'd not heard of "Tiffin Street". So I popped the street name into Maps on my iPhone and was suprised...

Photo Nov 13 7 14 23 PM

I tried a couple of times at different zoom levels and settings but Apple Maps would not show me a "Tiffin St" anywhere in Keene.

So I flipped over to Google Maps, still on my iPhone, and of course there it was:

Googlemaps

And indeed I went by the street on my lunchtime run today and can confirm to Apple with my own eyes that Tiffin Street does indeed exist in Keene!

Tiffinst

Hopefully Apple will continue to improve their data, because this is really quite silly!

P.S. I guess the good news is that I now know where "Giffin St" is in Keene... but that's not what I wanted! :-)


If you found this post interesting or useful, please consider either:


Why I Will NOT Be Rushing To Upgrade To Evernote 5 For Mac

Evernote5formacThe team at Evernote is making a big push right now to let users know about the upcoming new Evernote 5 for Mac. They have even released a beta version for users to try.

I won't be trying it. I'll wait for others to take the chance.

Why not?

Primarily because...

Evernote completely burned me with their "upgrade" of Skitch!

This "redesigned" Skitch took away pretty much everything that I loved about the application. Now I realize that the Skitch development team is different from the developers behind the main Evernote app, but still...

they have lost my trust.

Further, I have been so burned in the past by other software companies that whenever I hear (as I do in the Evernote 5 video) the words "we've completely redesigned the application", I immediately think:

NOOOOOO!!!! THEY ARE GOING TO TAKE AWAY ALL THE POWERFUL FEATURES I LIKE!

Evernote did it with Skitch. Skype did it with their Skype 5 for the Mac that left behind so much of the Skype 2.8 that we all loved. Apple's done it too many different applications to count (ex. iMovie, Final Cut).

So I cringe whenever I hear the words "completely redesigned"!

Now, granted, I do appreciate it when companies take in user feedback and make new versions of their applications. I love it when companies are responsive and make applications better. I just don't like it when they remove powerful functionality (even as I do understand that sometimes they need to do this to re-do the application).

For me, Evernote is a critical part of my daily workflow. I am a paying Evernote customer and use it across my multiple systems and mobile devices.

I don't want that workflow screwed up!

So I will wait for a bit and see what others who are more daring than I say about the new version. I am pleased to see that the initial comments to the beta release post seem to be positive. I'll continue to monitor the flow of comments for a while before I even think about upgrading.

What about you? Are you going to take the plunge?

FYI, here's their video about Evernote 5:


If you found this post interesting or useful, please consider either:


Ameche Lets Telcos Add Apps Into Regular Phone Calls To Add Value And Services

AmecheImagine you are driving fast along a major highway in traffic and you receive a call from a critical customer. She wants to know immediately when you can meet tomorrow with her team to go over the final proposal and sign the deal. There's no way for you to pull over and look at your calendar on your phone or computer... and it's really not safe in the high-speed traffic for you to be flipping through your calendar while you talk. What do you do?

Do you tell her you'll give her a call back when you get to a safe place? Or do you do the unsafe action of looking at your calendar on your phone?

What if there was a different way?

What if you could say something like "Let me check my calendar for tomorrow at 3pm" and then suddenly have a voice whisper back to you - on your call, but only heard by you - "your calendar is free at 3pm. You have meetings at 2 and 5."

You could then reply to your customer after just this brief pause letting her know that you could meet with her.

Sound like science fiction?

Perhaps... but that is the type of functionality that the team over at Voxeo Labs is looking to bring to calls with the launch of their new cloud service offering called Ameche. They are using the tagline "Apps in your Calls™" and produced this brief video to talk about what can be done:

I admit that I find their overview page and their introductory blog post a little bit over-the-top in terms of marketing-speak, but it starts to get interesting to me when you look at the page about apps in your calls. I'm not sure that I personally would get too excited about the "Social Calls Status Updates" example but it is extremely cool and valuable that they have this capability to connect with social networks. I find the other use cases such as Salesforce.com integration and context-based routing, and including the case I described at the beginning, far more compelling. It's also very important to note, as they do farther down that page, that Ameche is a platform and so can be used to build many different types of applications:

Ameche possibilities

That platform itself, described on the Ameche technology page, sounds quite intriguing. As I understand it, they are essentially deploying a virtual machine running Node.js into a carriers network and then deploying applications inside that VM. They provide this network diagram showing how the pieces can fit together:

Ameche technology

The outstanding part here is that they are using common web programming languages and fitting directly into existing carrier networks. This platform will let telcos create new services that can work with existing phone connections and existing phone numbers. No need for the customer to do anything except order the new service. No apps to download, no numbers to configure.

Obviously the primary market for this service is really the telecommunications service providers / carriers who are looking to offer additional services to their customers. At a time when those telcos are so threatened by the rise of various VoIP services and are looking for ways to build customer loyalty and keep the customers from leaving, Voxeo Labs' Ameche may just be the type of platform those carriers need right now.

Congrats to the team at Voxeo Labs on this launch - and I look forward to seeing what telcos will build with this new platform!


Full disclosure: I worked at Voxeo for 4 years and as a result am a small shareholder in the company. However, I would not write about the company or its products unless I thought they were worth writing about.


If you found this post interesting or useful, please consider either:


Got an IPv6-enabled app? Enter this Application Contest for a 10,000 Euro prize!

Have you created an application that does something unique or interesting with IPv6?  Or makes use of new capabilities that come with IPv6?   Or have you expanded an existing application so that it now works with IPv6?

If so, consider entering the International Application Contest 2012 sponsored by the IPv6 German Council.  As noted on the page about applications, the contest is open to “companies, groups or individuals of any nationality” and has a first prize of 10,000 Euros!  The deadline to apply is October 24, 2012.

Do note the judging criteria listed further down the page:

  1. What contribution is made to create a new Internet experience?
  2. How will the contribution promote and spread IPv6, the next Internet protocol?

It’s great to see contests like this out there – and we look forward to seeing what applications are submitted.

Want to get started with your application? Check out our suggestions for developers!

AdhearsionConf 2012 Call For Speakers Ends Tomorrow (Sept 8)

Adhearsionconf2012Do you like building telephony apps with Adhearsion? Have you built a really cool app that is worth sharing? Or used Adhearsion in an unusual way? Are you planning to attend AdhearsionConf 2012 in Palo Alto on October 20-21? Or would you attend if you could speak?

If you answered yes to any of the above questions, why not consider applying to be a speaker? The call for speakers is at:

http://adhearsionconf.com/call-for-speakers/

The only catch is ... the deadline is TOMORROW, Saturday, September 8th!

Ever since I first saw Jay Phillips present about Adhearsion back at one of the early ETel conferences in maybe 2006 or so I've been intrigued by how easy Adhearsion made it to develop telecom apps. It's just incredibly simple to make powerful apps.

If you are a Ruby developer (or want to be) and you are interested in building telephony apps, Adhearsion is definitely worth a look... and if you do use Adhearsion, why not consider signing up as a speaker?


If you found this post interesting or useful, please consider either:


Yea! Facebook’s iPhone/iPad App Finally Stops Sucking!

Hooray! With an update today Facebook's iOS app for the iPhone and iPad finally stops being so terrible! Lately using the application on my iPad was an exercise in futility outside of just simple likes or comments. If I ever tried to follow a link, this was what usually greeted me:

Facebook ipad before

It would sit there and sit there and sit there... and often what I would do was hit the arrow in the upper right to open the link up in Safari on the iPad. The link would typically load almost immediately in Safari and I'd be reading the page. Then when I flipped back to the Facebook app I would just hit the back arrow to go back to reading the stream.

The ONLY reason I really continued to use the Facebook app at all was because it was easier to use than the straight Facebook website when it came to liking posts. In using the website on the iPad I often found I had to tap the "Like" link twice to make it work - or not. It was inconsistent, where the app generally always worked.

I just dreaded having to open a link in the app.

And then today with little fanfare outside of an update from Mark Zuckerberg, Facebook released version "5.0" of the iOS app through the AppStore:

Facebook update

Upon learning about the new release from my own Facebook stream of updates (thanks, Dameon!), I updated the app on both my iPhone and iPad and was immediately pleased by the performance improvement.

MUCH faster! Kudos to the Facebook team for making the application actually pleasant to use!

In a quick bit of usage there seem to be many other tweaks to the UI. One I found particularly pleasing was a numerical notification of new updates since the last time you refreshed the feed:

Facebook ipad new stories

I haven't yet used it enough to find new changes I dislike... I'm sure there may be a few... but at least the application now is much faster and more responsive.

Thanks, Facebook team, for getting this new release out!

And if you have the FB app installed on your iOS device, head on over to the AppStore to get the update!

What do you think? Are there still parts of the mobile experience that are broken? Will this new release make you want to use the app again? Or will you stick to the website?


If you found this post interesting or useful, please consider either:


3 Great Posts to Read About Why Windows Phone 7 Hasn’t Taken Off…

Windows Phone 7

Jumping online this morning I noticed this trio of great posts yesterday about Windows Phone 7 and why it hasn't taken off. The discussion was started off by Charlie Kindel, a former Microsoft general manager:

MG Siegler weighed in on his blog with:

And Robert Scoble posted a comment on Charlie's post that led then to his own post:

The comments on both Charlie Kindel's and Robert Scoble's posts are also worth reading. There were other articles on this theme, but these were the three I found most useful.

As to my own opinion, I'm definitely in Scoble's camp (to which Siegler also agrees):

It's ALL about the apps!

The device formerly known as a "mobile phone" is now a device to access all sorts of services, information, games, Internet sites and to send messages to people... and, oh yeah, it can make phone calls sometimes if you really want it to.

It's all about the apps... and until Microsoft is able to truly foster a strong application developer ecosystem it will remain, like RIM, a minor player in the mobile market.

Image credit: microsoftsweden on Flickr


If you found this post interesting or useful, please consider either:


Oops! Google’s GMail iPhone/iPad/iOS App Pulled From AppStore

Well, Google's iPhone/iPad/iOS app was there for a little bit in Apple's AppStore... but now it's been pulled down because of "a bug that broke notifications". I did download the app a few hours ago to my iPhone and iPad and saw the errors mentioned in the blog post on both the iPhone:

Gmail iphone error

and the iPad:

Gmail ipad error

It's too bad, because in my initial usage, the app seems to work very well. Here's a shot of my inbox that looks like, well, pretty much any other email inbox:

Gmail ipad inbox

As Google's blog post indicates, the app has some cool features and use of gestures. I'll be using it for the next few days to see how it works.

Meanwhile, Google's team is obviously going off to make the notifications work!


If you found this post interesting or useful, please consider either:


Is Skype Soon To Release New APIs? Skype Renames Public API And Extends "Plugged into Skype" Partner Program

Pluggedintoskype
Today brings two changes from Skype to their developer programs. First, in an effort to bring some clarity to their existing application programming interfaces (APIs), they have renamed the "Skype Public API" to be called the "Skype Desktop API." As noted in a Skype blog post:
In Aug 2004, we made the Skype Desktop API available to encourage third-party innovation and integration with Skype. The Skype Desktop API allows Partners to access Skype functionality through the Skype desktop client via a text-based command protocol. The intent is not to duplicate Skype functionality but to complement the Skype desktop client with additional features and/or capabilities (e.g., call recording).

This is the API that pretty much all developers have had to use until recently where you application interacts directly with a Skype client. This also means that you have to have a Skype client running to use the API, which has been an additional annoyance for many developers. Developers have long desired an ability to connect directly into the Skype cloud without needing to run a client. Many of us had hoped that "SkypeKit" would be that client-less connection... but it, too, requires a client.

UPDATE: Multiple friends pointed out to me that SkypeKit is a bit more nuanced than this. SkypeKit does NOT require a "full" Skype client, i.e. a full working version of the Skype program. It does, however, require a "runtime" component to be running on a local system. It is that runtime (for Linux, MacOS X, Windows) that then makes the connection out to the Skype cloud. While this may not be a "client", per se, it does still require Skype code running alongside your application. Many of us would like to see "web APIs" from Skype that let you connect in to Skype's cloud without any kind of additional required Skype software. It is those kind of APIs to which I am referring in the paragraph below.

We know, though, from conversations at conferences and events that Skype has been working on developing new APIs... and perhaps this renaming is a precursor to the release of those new APIs. We can only hope... as they have been a l..o..n..g.. time in coming.

The other bit of news was that Skype is now promoting the use of the "plugged into Skype" logo for products using the newly-renamed Desktop API. Previously this program was promoted for SkypeKit products when SkypeKit emerged from beta back in June 2011 . Again from the post:

Plugged into Skype lets Skype users know that the application is built by a partner to work on Skype but was not built by Skype.

There is naturally a page in Skype's developer site (login required) all about how you can use the logo, original image files, etc., etc.

All of this is good to see as Skype, like everyone, is trying to woo developers to build apps on their platform (and add them to Skype's new "App Directory"). Making their program clearer can only help. (And hey, this is only their, what? ... 6th attempt at a developer program? Eventually they may figure it out.)

Meanwhile... is this renaming setting the stage for the release of some new client-less APIs? Let's hope so...


If you found this post interesting or useful, please consider either:


The Creepy – And Insecure – Side of iOS and Android Apps

Want to see the dark side of mobile apps? Just read this great bit of research from Troy Hunt:
Secret iOS business; what you don’t know about your apps

As people have noted in the comments, "iOS" (Apple's operating system for iPhones and iPads) is purely the platform Troy Hunt did his research on... but he's really talking about issues with mobile applications.

I'm my unfortunately sure that these type of issues will also be there on apps on Android and probably on other mobile operating systems from Microsoft, RIM, WebOS, etc.

These are application design issues.

The article starts off with the incredibly inefficient case of stuffing large images from "regular" websites down the mobile pipe to the phone... and then simply "resizing" them with "width" and "height" attributes. This is just laziness"efficiency" on the app developers part in that they are simply "repurposing their existing content" for a mobile audience, i.e. it's too much work/effort for them to create and track a separate smaller image for a mobile environment so they will just send you the larger one and eat up your data plan bandwidth.

But Troy Hunt goes on to talk about far worse issues... he calls out the analytics sent back to Flurry.com in particular (and there are other similar players out there) that report what the user is doing. I agree with Troy Hunt's comment that where this gets "creepy" for me is not so much reporting data back for one application, but rather that all this data is being aggregated across applications inside of Flurry's databases.

And then the truly scary issue of how little security some applications use to protect login credentials (i.e. NONE!) or to protect confidentiality of the information people are seeing.

As Troy Hunt points out with regard to the Facebook app for iOS:

Unfortunately, the very security that is offered to browser-based Facebook users is not accessible on the iPhone client. You know, the device which is most likely to be carried around to wireless hotspots where insecure communications are most vulnerable.

Mobile devices are being brought to the worst possible WiFi environments... and per this article seem to have some awfully insecure apps running on them.

Every mobile developer needs to read this article - and start looking at how to secure their apps!

P.S. Thanks, Troy Hunt, for writing this piece!


If you found this post interesting or useful, please consider either: