iPhone-App und iPhone optimierte Webseite kombinieren

Freitag, 10 Oktober 2008 21:39 - Geschrieben von René Lindhorst

I think sites that are serious about cultivating iPhone users as their customers should strive for a three-tiered approach in the future:

  1. a minimal iPhone-friendly website that presents your site’s highest value content, and links to access your full website and your iPhone app from the App Store,
  2. a traditional website, and
  3. an iPhone app in the App Store.

[Build an iPhone Web App and an App Store App - Inside iPhone Blog]

Ich halte diesen Ansatz für wirklich sinnvoll, zumal man die für das iPhone optimierte Webseite auch als Übergangslösung nutzen kann, bis man das native iPhone-App fertig hat.

Ähnliche Beiträge:


Cappuccino – Web Application Framework unter LGPL veröffentlicht

Freitag, 5 September 2008 21:02 - Geschrieben von René Lindhorst

Cappuccino, dass Webframework welches u.a. hinter 280 Slides steckt und als Portierung von Cocoa in JavaScript bezeichnet wird, wurde nun unter LGPL veröffentlicht.

[...] Cappuccino is about building applications, not web pages. When you think about applications, think 280 Slides, or GMail, or Meebo. jQuery, Prototype, and others do a great job of making static web pages a little more interactive, but they weren’t designed for building full fledged applications. Similarly, Cappuccino is not for building web pages; it’s optimized for a completely different set of tasks.

280 Slides is the first app built on Cappuccino, and it’s a great showcase of what’s possible. Cappuccino builds in many of the features you see, like the Document architecture, object copy/paste, global undo and redo, drag and drop, and great graphics support.

[Cappuccino Blog » Blog Archive » Announcing Cappuccino]

cappuccino-icon.png

Bei Theocacao gibt es einen “First Look at Cappuccino and Objective-J”:

[...] The executive summary is that Cappuccino is re-implementation of many of the basic parts of Cocoa, and Objective-J is a language which looks nearly identical to Objective-C and “compiles down” into JavaScript. You can also use JavaScript right inline with Objective-J, similar to how you can use C in Objective-C. [...]

[...] Xcode and Interface Builder are now reasonable prototyping tools for web apps based on Cappuccino, and Mac programmers can now quickly become very effective client-side web developers. [...]

[Theocacao: First Look at Cappuccino and Objective-J]

Links:
Cappuccino Web Framework
280 Slides – Create & Share Presentations Online
Theocacao – First Look at Cappuccino and Objective-J

Ähnliche Beiträge:


Ruby on Rails Bücher von O’Reilly kostenlos

Donnerstag, 4 September 2008 19:33 - Geschrieben von René Lindhorst

Für alle die sich näher mit dem Webframework Rails auseinandersetzen möchten gibt es nun von O’Reilly zwei kostenlose Bücher:

Zwei Bücher zum Thema Ruby on Rails hat der Verlag O’Reilly in sein OpenBook-Programm aufgenommen. “Praxiswissen Ruby on Rails” und das “Rails Kochbuch” stehen zum kostenlosen Download zur Verfügung.

[Kostenlose Ruby-on-Rails-Bücher von O'Reilly - Golem.de]

Auch zu Adobe Flex 2 gibt es ein neues OpenBook von O’Reilly, Schnelleinstieg in Flex 2 von Roger Braunstein.

Links:
OpenBook: Praxiswissen Ruby On Rails
OpenBook: Rails Kochbuch
OpenBook: Schnelleinstieg in Flex 2

Ähnliche Beiträge:


MobileMe – Work in Progress

Mittwoch, 3 September 2008 20:19 - Geschrieben von René Lindhorst

Chuq Von Rospach, ein ehemaliger Mitarbeiter von Apple, über die Probleme von MobileMe:

The ultimate failure seemed to be more capacity planning mistakes than anything else, if I’m guessing right. but the ultimate failure was not being willing to tell Steve “we aren’t ready” and taking that heat.

[...]

Apple has the expertise; this isn’t a case of MobileMe problems crawling out into itunes, but Apple bringing the iTunes expertise into MobileMe. And having thrown Eddy Cue at the problem, that’s exactly what’s going to happen here.

[Chuqui 3.0: MobileMe Problems Show Apple Needs an Infrastructure Lesson]

Ähnliche Beiträge:


Königsweg für die Einführung einer neuen Software

Sonntag, 24 August 2008 14:58 - Geschrieben von René Lindhorst

Ein sehr lesenswerter Beitrag von Aaron Swartz darüber, wie man eine neue Software (Webanwendung) idealerweise einführen sollte (”Hollywood Launch” vs. “Gmail Launch”):

I’ll call this technique the Gmail Launch, since it’s based on what Gmail did. Gmail is probably one of the biggest Web 2.0 success stories, so there’s an argument in its favor right there. Here’s how it works:

  1. Have users from day one. [...]
  2. Try to get lots of feedback from these new invitees, figuring out what doesn’t make sense, what needs to be fixed, and what things don’t work on their bizarre use case combination. [...]
  3. Automate the process, giving everyone some invite codes to share. [...]
  4. Iterate: give out invite codes, fix bugs, make sure things are stable. [...]
  5. Take off the invite code requirement, so that people can use the product just by visiting its front page. [...]
  6. If all this works [...] then you can start building buzz and getting press and blog attention. [...]
  7. Start marketing. [...]

[How To Launch Software (Aaron Swartz's Raw Thought)]

Ähnliche Beiträge: