Do you know where to get inspiration as a frontend web developer?
Do you use AngularJS directives?
I don’t have any experience with CoffeeScript, but from just looking at it and reading blog posts I like the syntax.
My concern: “Debugging might be hard” is resolved by Martin
If I need to debug in that code, I can easily see how it matches up to the source CoffeeScript.
Marijn showed how he “extended” a HTML textarea to a full functional editor
Nice features of codemirror like:
-Integration of JSLint
-Search and Replace
How was it built:
-The cursor is a lie
-Scrollbars not real either
only the visible part is in the DOM
-dont be afraid of big files
B-Trees to the rescue
“If you lie to the user once you need to lie more and more”
Amazed how much work happens behind the scene, by something that seems so
#webmonday Native vs. Hybrid vs. Web Apps
Recap talks @ HP Zürich #MobileMondays and #WebMondays night
# Markus Leutwyler, HP: Web vs Native Apps
History of the web and mobile is repeating
- 10 years ago: Web: hobby programmers make web
- Now: Apps: lots of hobbists make apps?
Reasons for native:
- Offline mode
- Findability (Discoverability)
AppStore is less cluttered than Google?
- Device integration
Reasons for hybrid apps:
- Code reuse
- A common set of technologies
- Low barrier of entry
- Cross platform reach
- Familiar tools and techniques
- Not tied to an vendor market place (AppStore,…)
- Start an app from a URL (potentially)
- PhoneGap: Package website as an application
The OS is the browser!?
ChromeOS, HP webOS, boot2Gecko (FireFox)
# Colin Frei, Liip AG
works at LIIP, php in the backend, HTML+CSS
NIWEA.ch native interoperable web application
Other containers for hybrid apps
- Cocoon JS
PhoneGap is for: iOS, Android, WinPhone, BlackBerry (RIM)
Advantages of Hybrid
- Knowledge: lots of devs out there, heaps of knowledge
- 1 team that works on 1 code base
Instead of 1 guy that knows the iPhone app
- Portability: code can be easilty ported to different platforms
- Reusability: code can be reused
- Not everything is supported
You have device specific code
PhoneGap to wrap HTML+JS up and submit it to the AppStore
- In-App purchases: PhoneGap has a feature for that
- Notification service by PhoneGap
Good experience overall from Colin
- Submitting to Apple takes time to get used to
- Not many bugs.. released months ago
- HTML5: more and more functionality is going into the device
# Vikram Kriplaney: Founder of mobile @ local.ch
Reasons for going native
- Go beyond the standard usage
Use the whole native possibilities
- Be aware of Leaky abstractions:
"All non-trivial abstractions, to some degree, are leaky."(Joel Spolsky)
Goal: The more audience the more effort to put in
How do you test a mobile application?
- Manual? How can you automatically test on every change?
Automation and Manual and Internal Dogfooding
Do you measure feature usage per platform?
- Yes per platfrom with Google Analytics etc…
My 2c to this discussion
#1 Is it better to have a Porsche UI and a VW engine
than a VW UI and a Porsche engine.
Of course you want a Porsche UI and a Porsche engine, but
#2 The first impression is important!
You only get one shot. Or maybe 2
#3 A potential approach
- Start with a hybrid
Leverage 1 of those great frameworks to get something up and running quickly
- Measure (usage, performance, ..)
- If you need native (see measurements), go native
- Rinse and repeat
Great explanation about hoisting and how you should code for it: One “var” at the top of scope.
Awesome that JSLint can spot this.
Look up HTML5, CSS3, etc features, know if they are ready for use, and if so find out how you should use them – with polyfills, fallbacks or as they are
Websocket support is still not fully supported :-(