The official Basecamp iPhone app
37signals.com
The official Basecamp iPhone app
1–10 of 54 posts
Re: The official Basecamp iPhone app
#2I remember when they said the way to go was HTML5 and all that talk. Glad their changed their vision.
Re: The official Basecamp iPhone app
#3I remember when they said the way to go was HTML5 and all that talk. Glad their changed their vision.
It's a hybrid app, views written in HTML5 & CSS3, and wrapped on the device. Navigation is native.
(Source: the post)
Re: The official Basecamp iPhone app
#4From a friend I saw logging in, it seemed like the oauth webview screen (that 3rd party apps use to interact with the API) has been ditched for something native as well. Something 3rd party apps can never re-create.
Re: The official Basecamp iPhone app
#5I remember when they said the way to go was HTML5 and all that talk. Glad their changed their vision.
It's a hybrid app, views written in HTML5 & CSS3, and wrapped on the device. Navigation is native. (Source: the post)
I assume he is referring to Basecamp Classic Mobile [1]. Reading the post, it seems they thought HTML5 was the "way to go" because they had more experience with the technology, not for any particular technological reasons.
[1] http://37signals.com/svn/posts/2761-launch-basecamp-mobile
Re: The official Basecamp iPhone app
#6I wish they just put more effort into making their web interfaces more responsive. Trying to use Campfire from the browser on my Galaxy Nexus is nearly impossible.
Re: The official Basecamp iPhone app
#7Looks good. Shame there is no mention of Android at all.
The biggest thing I took away from this blog post was this.
"NOTE: Basecamp for iPhone requires an account on the new Basecamp (released March 2012). Basecamp Classic is not supported."
I wonder what % of users haven't switched over even after a year. I think this is a good lesson for anyone thinking about effectively launching a new product to replace one they already have.
The company I work for did a similar thing about 15 months ago. We still have about 10% of clients on the old system. We offered free upgrades to get everyone over but some didn't want it. New platform has now diverged sufficiently away from the old one that there is no direct upgrade path any more. This has effectively left 10% of clients stranded.
Looking back I think any replacement product needs to be 100% compatible and after x months clients are forced over. It causes some short term hassle and support costs but in the medium term really simplifies development work if old products are completely retired.
Re: The official Basecamp iPhone app
#8Simple, dumb questions: So what is the point of it being hybrid, actually? Speed of development? Multiple platforms?
Re: The official Basecamp iPhone app
#9Looks good. Shame there is no mention of Android at all. The biggest thing I took away from this blog post was this. "NOTE: Basecamp for iPhone requires an account on the new Basecamp (released March 2012). Basecamp Classic is not supported." I wonder what % of users haven't switched over even after a year. I think this is a good lesson for anyone thinking about effectively launching a new product to replace one they…
From my experience adoption of new versions is always pretty slow with 'normal' users. They don't care for new versions as long as the current version they're using gets the job done.
Re: The official Basecamp iPhone app
#10Seems a bit funny since just last September they blogged their mobile version and "no app required."
https://basecamp.com/1679267/announcements/10
One of the reasons I recall this is that I saved this particular e-mail newsletter at the time. I thought it of particular interest they dedicated resources on making a mobile browser performant version and had eschewed a mobile application approach. So what has changed or did they feel a deficiency in that version?