Discover Top Posts Tagged with #chris heilmann

Tormé 1986

#bernie torme #phil lewis #chris heilmann #ian whitewood #torme #tormé

App Web Progressive: il futuro del Web mobile

Nel nuovo eBook prodotto da Google, Microsoft & Awwwards, “App Web Progressive: il futuro del web mobile”, vengono analizzate le possibilità offerte dalle App Web Progressive di usufruire delle funzionalità e dell’esperienza utente delle App Native navigando da mobile.

Negli ultimi dieci anni i dispositivi mobile hanno rivoluzionato completamente il panorama digitale. Attualmente vengono…

View On WordPress

Microsoft realiza o seu maior evento do ano dedicado à Web e reúne mais de 350 participantes

Mostrar como a Web está a mudar e a adaptar-se à nova geração tecnológica, e de que forma Portugal pode liderar esse caminho tirando partido das novas plataformas existentes, foram os principais temas em análise ontem no Microsoft WebCamp, o maior evento do ano inteiramente dedicado à Web, criado pela Microsoft Portugal em conjunto com o ecossistema de Web Developers Nacional. (more…)

View On WordPress

#Beatriz Oliveira #Carlos Alexandre #Chris Heilmann #Cloud #comunidades Web #developers #Eventos Microsoft #Interoperabilidade #Jon Galloway #José Castro #Mat Velloso #Márcio Spínola #Microsoft Portugal #Microsoft WebCamp #Modern Web #Modern Web Standards #Peter Tilsen #Startups

Millennials might be selling themselves short with cash

They ended up being grownups in the midst of the Great Economic crisis, just old enough to see their moms and dads freak out about a sheer stock market crash. As a result, reports Forbes, many Millennials are choosing to make use of cash money as a long-term investment.

According to a Forbes post, about 39 percent of Millennials prefer cash money when they're talking about cash they don't anticipate to need for 10 years. While utilizing cash could help them feel much better and more secure, the truth is that this could trip up Millennials down the roadway.

One the one hand, says the article, Millennials understand the significance of saving. They "get" that they must get ready for the future and build their wealth. Nevertheless, a significant portion of them are going about it in the wrong way, thanks to the impression made by the current financial crisis.

Unfortunately, cash couldn't suffice in the long run. In order to truly build wealth for the long haul (think: retirement) and beat out inflation, you've to invest cash in stocks. Exactly what some Millennials do not understand is that, lasting, stocks have yet to lose total, and young people have time to benefit from down cycles (buy even more for less) as well as up cycles.

While having some money in the profile is not a bad thing for liquidity and safety, the truth is that if you want to efficiently grow your wealth over time, financial investments are required as well. Once Millennials discover a much better balance in that regard, they're most likely to do quite well economically.

#1 #Baby boomer #Chris Heilmann #finance #Millennials #Millennials might be selling themselves short with cash

Samsung Devcon - State of HTML5 - Chris Heilmann

#html5 #video #state of html5 #chris heilmann

Developer evangelists and onions

I wrote about what a developer evangelist is and about the purpose of an API strategy within which the developer evangelist plays a crucial role. Over the last two years I developed a developer evangelist model which I would like to describe here. Feel free to comment, criticize, re-use, or extend it. The beauty of this model is that it summarizes some of the most important types of activities of an evangelist and it is scalable. The model can be applied to a one-man-band evangelist as well as to a team of evangelists.

Here is how it works. The following figure shows the three main pillars at its core.

The three main pillars explained:

Events: As an evangelist you need to be present, at events, physically. These can be large developer conferences, developer days, barcamps, hackathons, workshops, or trainings. The difference between a developer day (e.g., bada developer day) and conference (e.g., API Strategy) is that a developer day is usually organized by one company or ecosystem player, whereas a conference is usually broader and covers more diverse topics. The physical presence is very important to be tangible by your audience and to add the personal touch to your product, which increases trust. It also helps tremendously in getting a better understanding of the real needs and pain points of developers.

Communication: Apart from physical presence a developer evangelist needs to be present in the virtual space and communicate. These can be ‘classical’ means such as an email newsletter or RSS, or social media such as blogs, twitter, facebook, or a Youtube channel. Ideally you segment your developers and provide relevant communication to each segment. In marketing-speak that is the segmenting—targeting—positioning process. I wrote about developer segmentation earlier, which may help. Finally, you want to let the community solve problems between its members. An open forum is a good means to achieve that. You could also outsource this to thrid parties such as StackOverflow like Netflix did.

Content: This is really the meat of the work of an evangelist. The quantity and even more important the quality of the produced content needs to be excellent. Relevant content in this regard are API reference documentation, simple getting started and how-to guides, sample code and open-source apps, app galleries (for inspirational food for thought), sandboxes or API consoles. Here is Apigee’s example of Twitter’s API console.

A very important maxim is simplicity. Developers have no time, so it must be crystal-clear what’s the benefit of your API or product and it must be dead-simple and quick to adopt. There is Pamela Fox’ notion of developer experience, which is a great guideline to follow.

In addition to the three pillars, we have a foundation and a top.

The foundation in my model is the constant sensing of the market or your community. That is achieved implicitly by being present in your community physically and virtually – as mentioned above – with open ears and eyes. But it should be enriched by explicit means to get a better understanding of the pains and potential gains of developers. Means can be online questionnaires, expert interviews, or focus groups, or a combination of these. I recently conducted a perceived-use value (PUV) analysis of an API program, where I combined expert interviews to identify new opportunities (features or services) with an online questionnaire to quantify these opportunities. The outcome was very insightful.

Sensing the market is very important to see on the one hand the impact of your work but on the other hand also to understand where the market is moving to, to spot opportunities and exploit them – e.g., by reporting insights to product development.

I call the top acceleration. You are not alone. Usually you work in a network of vendors and partners. These partners often have their own content distribution and communication networks and means. By working together mutually beneficial acceleration can be achieved. With the emergence of open APIs chances are increasing that your partners have API or developer programs themselves which can be leveraged.

Finally, here is why it is called "Onion" model. What I described so far is only the inner core. There are two more layers.

The second layer around the core is about pilot partner engagement. These are usually early adopters who you work very closely with to adopt your technology. This is hard work and very manual because you want to provide a very careful and personal support. Getting pilots live has two main advantages: First, you get great feedback about your technology deployed in a real life setting and you can improve it accordingly. Second, you can use a successful pilot as a case study example and for general promotion and awareness activities.

This leads then to the final ring in the Onion, which is about general awareness activities. This is pretty much using classic advertising, promotion and PR means to spread the word about your product. This targets more at the general public and less at developers directly. It is advisable to work closely with PR and marketing people or departments of your company.

As indicated by the arrow in the figure above pointing from the center outwards, the activities encapsulated by the Onion are less regionally focussed the more you move outwards. Events and communication can be very targeted and regional whereas general public PR is very broad and less regional.

Deploying several Onions

I mentioned at the beginning that the Onion is scalable. It is also adaptable. Ideally you would adapt the Onion to the particular segments. As an example consider the following scenario: you have two main categories you want to serve: big-head and long-tail developers (using Chris Anderson’s notion (see “The Long Tail”)). I call it ‘categories’ because for segments this classification is too rough. Secondly, you provide your APIs using two different access technologies: SOAP and REST. You can construct a matrix like the one shown in the figure below.

This matrix gives us four areas we need to cover with evangelist activities.

Let’s assume we don’t offer SOAP for the long-tail category (too much overhead, not popular, no adoption). Hence, there is no Onion in the fourth quadrant. We do provide REST for the long-tail, and in order to reach out to developers we deploy the whole onion except we don’t offer a pilot program for long-tail developers (second quadrant). On the other hand we do provide a pilot partner program for big-head developers, which are usually bigger brands but don’t do general awareness activities for this category (most of the work is done via direct work with leads) (see first and third quadrant). Finally, you can spot that in the first quadrant the content pillar is empty. We don’t specifically provide REST technology content for big-heads but refer to the content developed for long-tails.

This example should show how you can scale and adapt the Onion and deploy various of them customized for your developer segments.

Key take-away:

As Chris Heilmann wrote in his Developer Evangelist Handbook -- which I also described in the post “What is a developer evangelist” -- the work of a developer evangelist is very diverse and so is the skillset. With the Onion model I try to bring this into a picture to structure this and to bring it in relation to each other. The Onion should also help to focus and prioritize and it will also show you which activities you need to do more of for which developer segment. Finally, it should also help in scaling your work, for instance, if you need to build an evangelist team and if you need to identify the skills you need to look out for.

#developer evangelist #developer segments #Chris Heilmann #long tail #Chris Anderson #Onion #segments #evangelist #documentation #developer day #conference #sample code #pilot partner #REST #SOAP #perceived-use value #events #social media

HTML5 doesn’t perform?

HTML5, on the other hand by its very definition is a web technology that should run independent of environment, display or technology. It has to be as flexible as possible in order to be a success on the web. In its very definition the web is for everybody, not just for a small group of lucky people who can afford a very expensive piece of hardware and are happy to get locked into a fixed environment governed by a single company.

Native applications need to be written for every single device and every new platform from scratch whereas an HTML5 App allows you to support mobiles, tablets and desktops with the same product. Instead of having fixed dimensions and functionality an HTML5 App can test what is supported and improve the experience for people on faster and newer devices whilst not locking out others that can not buy yet another phone.

Native Apps on the other hand do in a lot of cases need an upgrade and force the end user to buy new hardware or they’ll not get the product at all. From a flexibility point of view, HTML5 Apps perform admirably whilst native applications make you dependent on your hardware and leave you stranded when there is an upgrade you can’t afford or don’t want to make. A great example of this is the current switch from Apple to their own maps on iOS. Many end users are unhappy and would prefer to keep using Google Maps but can not.

HTML5 can not be monetized?

...

HTML5 is a technology stack based on open web technologies. Saying that HTML5 has no monetization model is like saying the web can not be monetized (which is especially ironic when this is written on news sites that show ads).

...

HTML5 can not be offline?

...

You can also store the application itself offline using AppCache which is supported by all but Internet Explorer. If you have more complex data to store than Web Storage provides you can use either IndexedDB (for Chrome and Firefox) or WebSQL (for iOS and Safari). To work around the issues there are libraries like Lawnchair available to make it easy for developers to use.

HTML5 has no development environment?

...

For the more visual developers Adobe lately released their Edge suite which brings WYSIWYG style development to HTML5, including drag and drop from Photoshop. Adobe’s Edge Inspect and PhoneGap makes it easy to test on several devices at once and send HTML5 Apps as packaged native Apps to iOS and Android.

..,

Things HTML5 can do that native Apps can not

Write once, deploy anywhere

Share over the web

Built on agreed, multi-vendor standards

Millions of developers

Consumption and development tool are the same thing

Small, atomic updates

Simple functionality upgrade

Adaptation to the environment

#Chris Heilmann #html5 #myth #mobile apps #mobile dev

Images in HTML

Dies ist eine Zusammenfassung des Artikels: "Images in HTML" von Chris Heilmann

Bilder ja/nein

Achtung! Es gibt Gründe warum man nicht immer Bilder für eine HTML nützen sollte:

User die mit mobilen Geräten surfen, schalten Bilder wegen dem sowieso kleinem Bildschrim, oder der hohen Datenrate aus

Blinde oder sehbehinderte Menschen können Bilder gar nicht, oder wenn dann nur schlecht sehen

Menschen mit anderem kulturellen Hintergrund nehmen Symbole evtl. anderst war

Suchmaschinen analysieren (bisher) nur Text, keine Bilder

Deshalb: Bilder intelligent einsetzen und evtl. eine Alternative anbieten.

Einbinden der Bilder in HTML

Wichtig:

Wenn das Bild für den Inhalt der Seite wichtig ist, sollte es direkt im HTML (<img> Element) und mit dem passenden alternativen Text eingepflegt werden.

Wenn das Bild nur als Verschönerung dient ist es sinnvoller dies mit CSS einzubinden

Und so wird das JPG Beispielbild eingebunden:

hier ist zu beachten, dasss das Bild im selbern Ordner wie die index.html liegen muss!

Bei diesem Befehl wird das Bild zwar angezeigt, die HTML ist allerdings nicht valide. Hierfür wird ein alternativer Text (<alt>) benötigt. Wird das Bild aus einem bestimmten Grund nicht angezeigt (z.B. Bild kann nicht gefunden oder geladen werden, der Browser unterstützt keine Bilder oder ein User mit Seheinschränkungen ließt die HTML mit einer bestimmten Software), so tritt der "alt-Text an die Stelle des Bildes". Deshalb sollte dieser so aussagekräfitig wie möglich sein.

Achtung! Nicht mit zusätzlichen Informationen verwechseln die auftauchen wenn der Mauszeiger über dem Bild liegt. Hierfür gibt es das <title> -Attribut.

longdesc - Ausführliche Beschreibung

Bei komplexen Bildern, zum Beispiel Schaubildern gibt es das <longdesc> - Attribut. Dieses Attribut verweist auf eine seperate HTML mit ausführlicher Beschreibung. Dies ist visuell nicht festzustellen, wird aber von Screenreadern erkannt und an die Userweitergegeben, ob sie den longdesc nutzen wollen.

Beispiel:

das Bild (inlineimagelongdesc.html) mit "longdesc-Attribut":

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>Example of an inline image with longdesc</title> </head> <body> <img src="chart.png" width="450" height="150" alt="Chart showing the fruit consumption amongst under 15 year olds. Most children ate Pineapples, followed by Pears" longdesc="fruitconsumption.html"> </body> </html>

die "longdesc-HTML" (fruitconsumption.html):

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>Fruit consumption</title> </head> <body> <table summary="Fruit Consumption of under 15 year olds, March 2007"> <caption>Fruit Consumption</caption> <thead> <tr><th scope="col">Fruit</th><th scope="col">Amount</th></tr> </thead> <tbody> <tr><td>Apples</td><td>10</td></tr> <tr><td>Oranges</td><td>58</td></tr> <tr><td>Pineapples</td><td>95</td></tr> <tr><td>Bananas</td><td>30</td></tr> <tr><td>Raisins</td><td>8</td></tr> <tr><td>Pears</td><td>63</td></tr> </tbody> </table> <p><a href="inlineimagelongdesc.html">Back to article</a></p> </body> </html>

Schnellere Bilder

Standardmäßig weiß ein Browser nicht die Größe der Bilder. So läd er erst den ganzen Text und passt diesen dann an, wenn das Bild geladen ist. Dies kann man umgehen wenn man die Größe des Bildes schon vorher angibt. Somit wird dieser Bereich gleich für das Bild freigehalten. Zwar kann man das Bild auch per HTML sklieren, dies sollte aber vermieden werden. HTML skaliert zum einen die Bilder nicht verlustfrei und andererseits wird bei einem kleiner skaliertem Bild das Quellbild geladen, was sinnlose Ladezeit verursacht!

CSS

Wenn es darum geht Bilder in irgendeiner Art und Weise in der HTML auszurichten: CSS benutzen. HTML hat zwar auch ein paar dafür, ist aber lange nicht so einsetzbar und flexibel wie CSS. Somit ist die Ausrichtung mit HTML passé.

#Chris Heilmann #HTML #Stefan Brenner