41–50 of 54 posts
"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…
Earlier quoted context omitted.
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 swi…
> as any good web developer will know.
Am I missing something here? Pretty sure I haven't written 2 books, decrying overhead and the ills of appeasement. 37signals have 2 books (which I've read) that clearly illustrate why you should avoid scope/feature-creep – especially for the cost of satisfying a few people. The avoidance of a native app followed this lineage.
I've watched the slow, articulated steps from "bootstrapping", Jeff Bezos, "this is different because X", etc. It's all very well and good, but you've charged people $. Like any customer, expectations are there.
So I am to ignore hundreds of pages of text because we all don't have the books in front of us right now for reference?
My overarching point is, if you're going to sell me an ideology - stay with it.
Earlier quoted context omitted.
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 swi…
I'm not suggesting a 180 degree about-face. And if we were talking about a company that didn't sell philosophy in the form of books and blogs, my point would have much less relevance. > as any good web developer will know. Am I missing something here? Pretty sure I haven't written 2 books, decrying overhead and the ills of appeasement. 37signals have 2 books (which I've read) that clearly illustrate why you should av…
I don't know how anybody could interpret this as anything but a complete about-face. Ditch being the key word. For your analogy to make sense, 37 Signals would have had to ditch html/css/javascript as their main stack for the mobile app, which they clearly did not.
Worth noting: this was built using RubyMotion ( http://www.rubymotion.com/ ).
Earlier quoted context omitted.
I'm not suggesting a 180 degree about-face. And if we were talking about a company that didn't sell philosophy in the form of books and blogs, my point would have much less relevance. > as any good web developer will know. Am I missing something here? Pretty sure I haven't written 2 books, decrying overhead and the ills of appeasement. 37signals have 2 books (which I've read) that clearly illustrate why you should av…
"So, should we expect 37signals to ditch "bootstrapping" over VC-funded startups soon?" I don't know how anybody could interpret this as anything but a complete about-face. Ditch being the key word. For your analogy to make sense, 37 Signals would have had to ditch html/css/javascript as their main stack for the mobile app, which they clearly did not.
I have a problem with people speaking from authority, claiming their philosophy works well (which I agree with) and then slowly proposing the opposite. Again, as a frequent reader of their posts and philosophy, I'm confused as to why providing reference to this philosophy is considered blasphemy.
I'm also confused by the very vocal and opinionated damning of security in other platforms by DHH while Rails suffers security issue after security issue. Suddenly, DHH isn't all that opinionated on security. And I'm the jerk for pointing this out, right?
I know every person who disagrees with DHH or JF is automatically a troll without examination, but I'm a little tired of being considered a 37signals hater while I pay monthly for Basecamp, purchase their books and follow their line of work.
Worth noting: this was built using RubyMotion ( http://www.rubymotion.com/ ).
Simple, dumb questions: So what is the point of it being hybrid, actually? Speed of development? Multiple platforms?
Both, and more. We're aiming to post a series of articles on Signal vs. Noise about the decisions we made.
Earlier quoted context omitted.
"So, should we expect 37signals to ditch "bootstrapping" over VC-funded startups soon?" I don't know how anybody could interpret this as anything but a complete about-face. Ditch being the key word. For your analogy to make sense, 37 Signals would have had to ditch html/css/javascript as their main stack for the mobile app, which they clearly did not.
Sorry, this bit about ditching is tongue-in-cheek. I don't actually expect them to do so, although I do feel that eventually this will happen and we'll all be back here discussing why it's different because of X . I'm also confused why the overwhelming majority of HN readers manage to claim that a HTML5/PhoneGap app is inferior to a native one, but then somehow bob and weave when 37signals does the same thing. Confus…
I agree with you there; it is confusing.
Earlier quoted context omitted.
Looking back I think any replacement product needs to be 100% compatible and after x months clients are forced over. I actually think this is a ploy to get their users to convert. 37signals has a strong "we let our users outgrow us" stance, so what I read between the lines is that 37signals sees no hassle continuing to support the old system (it's massively profitable). Dually it gives a better justification for an u…
I'd love to take credit for a brilliant strategy, but this isn't one of them. The story is very simple. We released an iPhone app for the all new version of Basecamp. Nothing more, nothing less.
"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…
> So we stopped and thought about it for a bit. Do we want to have to hire an iOS developer and an Android developer? That’s a lot of specialization, and we’re usually anti-specialization when it comes to development.
I don't mind it when people change their minds about something, its a sign of intelligence, but if you're going to do it after having taken such a hard stance against the position you are now in favor of, at least do the intellectually honest thing and at least say "Yeah, we weren't in favor of this before, but we changed our minds. here's why" instead of acting like it never happened.