You can now forward in voice mail to Torch Project Management from services like Google Voice and have them associate to the proper project based on phone number. In Google Voice from the "more" menu you can select to e-mail the voice mail. Once Torch receives the message it will look at the phone numbers of the external users associated with each project and determine the proper place to import the message.
Archive for August, 2009
James phone: 509|206
This would find someone named James in the 509 or 206 area code. Despite its name, the phone bucket selector actually searches the phone, mobile and fax fields.
You can now also forward in voice mail from services like Google Voice and have them associate to the proper prospect based on phone number. In Google Voice from the "more" menu you can select to e-mail the voice mail:
Which will be imported into Heap like so:
Over the last 24 hours I've received some concerns about the new HTML5 mobile interface for Heap and Torch. Confusion is to be expected, especially as of this post's date there is really only four HTML5 apps of this type in use, so Heap or Torch's Mobile interface is likely the first such app people have come across. This post is to clear up some misimpressions and to explain why I think this is the future of all mobile productivity apps.
How does an HTML5 application start?
After you click the Heap or Torch icon on your home screen you will see the following sequence of screens:
There are a few key points:
- The interface becomes available to you as soon as the data is loaded from the local database (regardless of your online state)
- The sync process runs in the background so you can continue to view/create content while it is working
- The application itself runs directly off the device
How does the upgrade process work?
Whenever you are on the Internet and are using an HTML5 app, your device checks a small text file called the "manifest" to see if it's version is the same as the current version on the server. If not, it downloads the new application files to the device (in the background). The next time the app starts up you will be using the new version.
But perhaps the most important point is that the new HTML5 apps are not iPhone/iPod Touch or Android specific. There is not one line of platform specific code, it all conforms to the HTML5 draft spec.
Now compare the above to a native iPhone app:
- It only works on the iPhone / iPod Touch
- Upgrades require being submitted to Apple for approval (which takes some time) then installed by the user through Apple's App store
- Which (item 2) causes an issue of multiple versions of the app being in production at any given time because some users won't upgrade. This results in having to leave old "hooks" open in the server version of the application.
At current there are two issues:
- It doesn't work with the iPhone 2.x software
- It doesn't work with the Palm Pre
For iPhone users the upgrade is free, so there is really no reason not to upgrade. For iPod Touch users it is $10.
While the Pre implements some of the HTML5 spec, it doesn't implement all of the methods that the apps need (but once they are it will just work).
I'm pleased to announce a major new feature for Heap CRM: Offline Mobile Access. You can view messages, comments, uncompleted events, people on your active prospects regardless if you have an Internet connection. You can also add content (messages, events, people) and check-off events while offline.
But what is perhaps more exciting is how this is accomplished. Inspired by the great work done by the Gmail team and the support for HTML5 and Gears on the iPhone 3.0 and Android platforms, this mobile interface behaves like a hybrid of a web app and a native app. Like a native app it’s crazy fast and operates offline because the software and data is located on your device. However, like a web app it can be updated on a regular basis (without the user having to upgrade) and it works on a number of devices. In fact, as more devices support HTML5 they will “just work” with this new interface.