Live data from Hacker News

The official Basecamp iPhone app

37signals.com

31–40 of 54 posts

Re: The official Basecamp iPhone app

#32
"Eventually we came to the conclusion that we should stick with what we’re good at: web apps. We know the technologies well, we have a great development environment and workflow, we can control the release cycle, and everyone at 37signals can do the work. It’s what we already do, just on a smaller screen. We all loved our smaller screens so we were eager to dive in. Plus, since WebKit-based browsers were making their way to the webOS and Blackberry platforms too, our single web-app would eventually run on just about every popular smartphone platform.", Jason Fried, http://37signals.com/svn/posts/2761-launch-basecamp-mobile

So, should we expect 37signals to ditch "bootstrapping" over VC-funded startups soon?

Let me be clear, I'm not out to troll 37signals. But here's the thing, if you claim a superior ideology, sell that ideology on paperback and then go against your own methodology, you're going to get some feedback. You can't claim that everyone is a troll, or a "cesspool" whenever people confront these ideas - especially when you're selling them for $.

Re: The official Basecamp iPhone app

#34
post #32

"Eventually we came to the conclusion that we should stick with what we’re good at: web apps. We know the technologies well, we have a great development environment and workflow, we can control the release cycle, and everyone at 37signals can do the work. It’s what we already do, just on a smaller screen. We all loved our smaller screens so we were eager to dive in. Plus, since WebKit-based browsers were making their…

You couldn't possibly have read the article. They took a hybrid approach, which means that the vast majority of the app is still written in html/css/javascript. "The page stacking behavior and navigation menus are native while the rest of the screens are web views." - straight from the article.

So a more apt analogy than yours might be "we should expect 37signals to continue bootstrapping but also take a small loan from a bank to cover short term expenses".

Re: The official Basecamp iPhone app

#35
post #32

"Eventually we came to the conclusion that we should stick with what we’re good at: web apps. We know the technologies well, we have a great development environment and workflow, we can control the release cycle, and everyone at 37signals can do the work. It’s what we already do, just on a smaller screen. We all loved our smaller screens so we were eager to dive in. Plus, since WebKit-based browsers were making their…

You couldn't possibly have read the article. They took a hybrid approach, which means that the vast majority of the app is still written in html/css/javascript. "The page stacking behavior and navigation menus are native while the rest of the screens are web views." - straight from the article. So a more apt analogy than yours might be "we should expect 37signals to continue bootstrapping but also take a small loan f…

I did read the article. Both of them, actually. It was clear that most of the app is HTML5, CSS, JS. As originally stated in their previous post, they aren't keen on developing for multiple platforms natively. What they have released goes against the "write once, run anywhere" message that they've been selling for years. I'm quiet familiar with the tech stack they are developing on and so I know that while most is HTML5, there is definitely a development cost if they choose to go cross-platform. It's not as simple as you're alluding.

Re: The official Basecamp iPhone app

#37
post #35

Earlier quoted context omitted.

You couldn't possibly have read the article. They took a hybrid approach, which means that the vast majority of the app is still written in html/css/javascript. "The page stacking behavior and navigation menus are native while the rest of the screens are web views." - straight from the article. So a more apt analogy than yours might be "we should expect 37signals to continue bootstrapping but also take a small loan f…

I did read the article. Both of them, actually. It was clear that most of the app is HTML5, CSS, JS. As originally stated in their previous post, they aren't keen on developing for multiple platforms natively. What they have released goes against the "write once, run anywhere" message that they've been selling for years. I'm quiet familiar with the tech stack they are developing on and so I know that while most is HT…

You can make an argument that 37 Signals is still keeping with their web app philosophy. For their new iPhone app, it's a web app with an advanced native wrapper & navigation functions.

Re: The official Basecamp iPhone app

#38
post #7

Looks 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…

There's no mention of Android because this is an announcement for the iPhone version. We'll be addressing Android at another time.

That makes sense. I figure since most of the pages are web views, it wouldn't be that difficult to release an Android version when/if needed.

Re: The official Basecamp iPhone app

#39
post #35

Earlier quoted context omitted.

You couldn't possibly have read the article. They took a hybrid approach, which means that the vast majority of the app is still written in html/css/javascript. "The page stacking behavior and navigation menus are native while the rest of the screens are web views." - straight from the article. So a more apt analogy than yours might be "we should expect 37signals to continue bootstrapping but also take a small loan f…

I did read the article. Both of them, actually. It was clear that most of the app is HTML5, CSS, JS. As originally stated in their previous post, they aren't keen on developing for multiple platforms natively. What they have released goes against the "write once, run anywhere" message that they've been selling for years. I'm quiet familiar with the tech stack they are developing on and so I know that while most is HT…

Even with straight web browsers it's never 100% "write once, run anywhere" as any good web developer will know. You will always need to account for the idiosyncrasies of every browser, screen size, and system, and in the case of 37 Signals' new basecamp app, I see it as being no different. They most likely needed to gain access to some native apis and take advantage of a more reliable method of animating the page swipes.

And re-read your first post. You are suggesting that 37 Signals has done a 180 degree about-face, which is really unfair especially since you do actually understand the tech.

Re: The official Basecamp iPhone app

#40
I downloaded the iPhone app and tried it out. I'm actually quite impressed. The interactions are quite speedy and the app has a "native" feel to it. It also helps that the design of the app is quite nicely done.

I've been a big proponent of full native apps on mobile when possible. But this has got me thinking that the hybrid approach can be a smart move when done right.

Post reply on HN