Since I have promised to share a PureMVC site template a long time ago, and it is still bound to happen, I will now share another project I also built using the aforesaid framework.

This little project was built about four months ago, to solve a skill test for a Senior Flash Developer position in a London based agency. It took around 10 hours to complete during after-work time. A working demonstration is available here: http://demo.joaopescada.com/searchable-image-gallery/.

The Project.

The test required to develop a small image gallery in Actionscript 3 storing the images set in an XML file and allowing a tag based search functionality. Also, all coding should follow Object Oriented Programming through classes and Actionscript’s coding conventions and best practices.

The visual side of the application was also important. And, in my opinion, this is a point that marks a great difference between “hardcore” developers — with strong technical skills but, usually, low sensibility to visual design — and front-end developers in general, where a Flash Developer should be included. Any good front-end developer should comfortably know the elements and principles of design.

Take time defining the problem, and then solve it fast.

Having recently learned how to use PureMVC, this test seemed like a great way to strengthen my experience with the framework. It was fairly simple and only had to implement a couple of basic actions: show the photos with or without a tag filter applied and show each photo in detail.

For the visual layout, I opted for a grid-less structure simulating a real life environment: a wood floor with the photos scattered all over. It wasn’t the most common solution, but it was still easy to use and hopefully eye-candy enough to stand out from the crowd (the other developers applying for the same position).

The architecture.

As any regular MVC project, the classes needed to be grouped in three folders / packages: model (storing all the data that the app will need), view (where anything-visual is kept and the user actions are captured) and controller (providing communication between view and model).

The stage was created in a single Flash file using the Main class as the document class, with all the visual assets in the library being linked to classes in the view package.

Gluing it all together.

From this point on, you should have the source code nearby in order to check it as I briefly explain the logic behind it. The source code is available to browse and download at my GitHub repository: https://github.com/jpescada/PureMVC-AS3-Searchable-Image-Gallery.

Startup and the Controller.

It all starts in the Main class in the app package.

As soon as the stage is available, the AppFacade singleton is fired, initialising the PureMVC framework, overriding the sendNotification method — to allow debug control, by tracing the notification arguments — and registering the possible controller command calls with specific notifications:
- the StartupCommand is triggered by the STARTUP notification. It registers and initialises the data sources available (StageProxy, StateProxy and PhotosProxy), and the AppMediator (attaching it to the stage) and then requests a new photo search, without any filter applied, to populate the initial layout.
- the PhotoSearchCommand will listen for PHOTO_SEARCH notifications, handling all searches, through the PhotosProxy.
- the PhotoDetailCommand will respond to SHOW and HIDE notifications, setting the app state using the StateProxy, and showing or hiding the detail of a photo.

The Model.

The StageProxy allows access to the app stage, and dispatches notifications every time the stage is resized.
The StateProxy works as a central point to store information about the current state of the app. Namely the current photo selected, if any, and dispatches notification when the state is changed.
The PhotosProxy loads and provides methods to access the information stored in the XML, like search and returns the result coupled to a PHOTO_SEARCH_RESULT notification.

And the View.

The AppMediator registers mediators for the visual components of the layout: the GalleryMediator, the SearchBoxMediator and the DetailMediator.

The GalleryMediator controls the gallery movieclip on the stage, that will load and display the photo thumbnails. It subscribes to PHOTO_CHANGED, PHOTO_SEARCH_RESULT and STAGE_RESIZE notifications in order to update the gallery movieclip as needed. It also listens for clicks in the photo thumbnails and dispatches notifications to the AppMediator when it happens.

The SearchBoxMediator holds a reference to the searchBox movieclip on the stage. It subscribes to PHOTO_SEARCH_RESULT and STAGE_RESIZE notifications and dispatches a PHOTO_SEARCH notification when the user submits the search.

The DetailMediator is linked to the detail movieclip on the stage, updating the display when the subscribed notifications PHOTO_CHANGED or STAGE_RESIZE are received, and dispatches a PHOTO_HIDE notification when the user clicks on the detail movieclip.

All the visual components in the library linked to classes in the app.view.components package have simple methods to update the display or dispatch custom events that will then be picked up by the associated mediators and processed as need be.

Wrapping up.

This was an overview of the logic behind the app.
Feel free to browse and change the code to see what happens and learn with it.
If you end up facing problems or doubts, just drop me an email or comment using the form bellow and I will happily give you all the help needed.

Again, the source code is available here:
https://github.com/jpescada/PureMVC-AS3-Searchable-Image-Gallery.

and the working demo here:
http://demo.joaopescada.com/searchable-image-gallery/

Thanks for reading this article!

For updates on more articles like this, subscribe the blog’s RSS Feed.

This was on my to-do list for quite some time… now I can scratch it of the list!

I’ve been willing to share source code of “real world” projects where I’ve been involved for ages! Not that I see my work as something über-awesome or anything for that matter… But the same way I’ve been lost in code and ended up finding “The” solution in a post from some random mate on the other side of the globe, so can someone find this post — and future ones — as a resource of great value. And, as a bonus, leave work on time. :)

Sharing is a good thing. Really!

We, (Web / Flash / Interactive / Multimedia) Developers, live in a not-so-big community where rookies, juniors, seniors, gurus, veterans, ninjas and any-other-fancy-title-out-there need to work together in order to evolve our skills both personal and group-wise. And with working together I don’t mean geographically, but really as a whole cohesive community where we not only take from, but also give back in the same proportion.

With this in mind, and fueled by Nuno Ribeiro‘s talk at 2010 edition of FlashCamp Portugal — where he referred the must-read post of Marco Neves “Porque partilhar???“ (Why share??? by Google Translate) —, I’ve decided to create an online repository for sharing code at GitHub.

The project and its source code.

So, today was “The Day” and I finally published the first source code of a “real world” project I’ve worked on this year.
It’s a simple 3D scene with draggable cubes take cast shadows on the ground. A striped down version of the scene used in the website oonique candles for oon solutions.

It’s coded in Actionscript 3.0 using Papervision3D + JigLibFlash 3D physics library + Andy Zupko’s ShadowCaster + TweenLite for camera transitions and the help of loads of posts in blogs and forums all over the internet to overcome some problems I’ve faced during development.

As you can now infer, such a simple thing and — yet! — hundreds of people were involved so I could build up this one.

There aren’t much comments throughout the source code, but I’m always around if you need some help understanding something in it. Drop me an e-mail and I’ll write back.

The source code is available for download here: http://github.com/jpescada/PV3D-Boxes.

Go get your hands dirty and feel free to use it as you see fit.
This goes without saying, but any credits will be much appreciated.

For updates on more articles like this, subscribe the blog’s RSS Feed.

Now… I have to get back to work.
And thanks for reading till the end! :)

On October 2nd, took place the 2010 edition of FlashCamp Portugal at the auditorium of Universidade Lusófona. An event organized by AUG Portugal mainly for designers and developers working with — or just interested in — the Flash Platform.

It was my first time at this annual event, and at least one thing is for sure: I want to be back for next year’s edition!

Speakers and Talks.

Mike Jones – Designing Flex Components
Maybe because it was the first talk in the morning, or because it was a topic hard on the left side of the brain, it ended up suffering with an audience still in the waking-up process.
There were great tips explained, specially for someone who never built a Flex project, like me. It got me interested in the naming conventions used to create timeline transitions for the Flex Framework.

Paulo Fierro – Mobile projects
In my opinion, this was the best and most interesting talk of the day.
The case studies brought to stage revealed a good showcase of creative ideas pushed to production, just for the fun of it.
This was an inspiring talk. Period.

João Gonçalves / Francisco Costa, Paulo Afonso / Jorge Varandas, Nuno Morgadinho, Nuno Ribeiro – AUGPT Community Showcase
Gathering professionals from the community to show le crème de la crème was also a neat idea. It allowed to get a sense of the current market status. Great samples of work were presented, not only strictly digital, but also interactive installations.
As an extended bonus, some works were complemented with a technical background overview.
The most adverse presentation of the day was probably from Nuno Ribeiro, exposing mostly his personal opinions on the portuguese scene and overall was much of a rant. One to get people thinking nonetheless.

João Saleiro – Skin Flex 4 apps with Spark
If the first talk of the morning suffered with a waking-up audience, this suffered with a falling-asleep one. It was right after lunch.
Though it was an interesting topic, it was very technical and specific. But somehow managed to explain how simple it now is to skin a Flex 4 app from a designer’s point of view.

Niqui Merret – Bugs Catch’em All
Another funny talk. Approaching the debug process with a positive and methodical perspective was the main subject. Practical solutions and tools were presented to help easing the daily routine of every (Flash) developer. Not much new, but one bug caught me off-guard: writing an empty switch statement can crash the player? Gotta try this!

Rui Silva – Internationalization in the Flash Platform
This was a general opinion: the hardest talk to keep people focused in.
But it’s a very important subject, specially if one’s developing a project for multiple international markets.

Lee Brimelow – My Head Hurts
Even being the last talk of the day, it was one that raised most people’s attention. Lee Brimelow is clearly an experienced speaker and brought the hot topics for the table. Handed out arguments to help choosing the right technology for the right project. Sometimes arguments felt a bit biased on Adobe (on Flash versus HTML5 subjects) but in general the pros and cons of both technologies, for both desktop and mobile platforms, were explained.

Generally speaking…

I felt that the whole event was well organized, and that a lot of people invested a lot of time putting it all together.

The coffee breaks were well distributed throughout the schedule. And it was a very good idea the pin swap to enter the prize raffle. As a suggestion: make it harder next time, so more people have to interact with each other. Speakers included! :)

Two negative points that worth mentioning:
- the lighting was mostly too low on the stage;
- the podium was too off-center, making people on the right side of the room adopt the strangest positions to make it till the end of the day without stiff neck pains…

Suggestions for the future.

A Twitter wall would be welcome. It would provide realtime feedback from the audience that (hopefully) tends to grow every year.

Wireless mics would be a good bet. Avoiding speakers from having to be stuck behind the podium in order to use the mic.

This goes without saying, but an event like this without wifi internet access is so… 1999? Sponsors for this, should not be hard to get! :)

This is a sensitive subject, but having people to pay something for the ticket will act as a filter. Only the ones really interested will reserve a seat, and come. And avoids unpleasant and near disrespectful comments from the audience. Be it online or offline.

And another tough issue: though it’s a portuguese event, there were international speakers present — and hopefully more will come in the next editions — so having more english-spoken talks would be a bonus for them and (who knows!) an international audience.

Just like I said in the beginning of this post, I really enjoyed being present in this event. And unless the sky falls down or something else catastrophic happens, I will be at next year’s edition.

‘Till then, keep up the excellent work!

Photo used in comp by atomicjeep.

As referenced in the title, this article is about coding Actionscript 3.0 in a Model-View-Controller design pattern, namely the PureMVC way.

Problems don’t exist. Only opportunities for creating solutions.

A few years back, when I started on web design / development, it was a one-man show. I then started working with other developers from time to time. Two years ago, I joined a team of Adobe Flash developers, and only then I realized how many routes a single coding task can take. We all have different approaches on coding and with this in mind, I felt the need to find a standardized way of developing Adobe Flash based websites / applications.

Last year, after a lot of online research on Actionscript frameworks, I found PureMVC to be the most stable, mature and — most importantly — well documented.

Kicking the tyres.

Before having other team members sharing my opinion, I had to try it myself and apply all the concept on a real project.

My first approach on this design pattern — by the time of publishing this article — is still to be available online. It’s nothing too fancy, but what’s on focus here, is the code holding the pieces together. It’s a structure built to support three websites with similar content for Casinos de Angola. Two websites are on an ongoing approval process, while the third is still to be designed.

“If anything can go wrong, it will.”

Having little to no experience using the MVC pattern, and a deadline to meet, it was a risky choice to make. But still, I opted to take this road. And so — validating the aforementioned Murphy’s Law — I failed the initial deadline.

The development process took waaaaaay longer than I expected. Not because there was a lot to code, but because there was a lot to learn in order to get a solid ground to start building with the chosen architecture.
A big learning curve of concepts before getting into any real coding is a bummer.

Happier programming.

What do you think about the idea? Sounds good, right? It feels even better!
The framework enables a loose coupling between resources allowing an easy development of really project independent components. Maybe this is geek / coder talk, but it feels a more Human-like communication between abstract project resources. Bare this in mind: the notifications are a bliss to work with!

Being an avid follower of the Don’t Repeat Yourself principle and a control freak for logical organization and standardization I chose to implement a Convention Over Configuration paradigm by specifying the website structure / layout in a single XML (Model) file.

As most developers, if I can avoid extra work, by automating processes, I do. Better yet: if I can avoid starting a new project from scratch, and just re-factor 10-15% code of a previous one, I SURE do. And that’s what happened. Having the website contents (Model/Proxies) automating the layout (View), only a few bits of the business logic (Mediators) had to be changed. Now THIS is (planned) code reuse!

Wrapping up…

“The concept of PureMVC may make the best of us shy away, but once you’ve got your head around the bare fundamentals, you’ll soon be flying your way around it.” — Ahmed Nuaman said it on the first tutorial on PureMVC I’ve read, and I could not agree more (though I’m still learning the flying part).

I’m currently — at the time I started writing this article — finishing the development of two video players with similar functionalities, and everything is running smoother and faster. The first player took around 7 hours to complete. The second one? 45 minutes!

One of the biggest conclusions I found with this road I took was that allowing myself to fail, brought an enormous bandwagon of knowledge and rewarding experience. Only by trying harder and harder every now and then, and subsequently failing a lot of those times, you will broaden your comfort zone and therefore your horizons.

Maybe there’s an influence here from the OFFF’s 2009 edition theme: “Fail Gracefully” and the “This isn’t flying, this is falling with style” quote from Toy Story.

Want to learn more about AS3 on PureMVC?

Follows a list of articles / tutorials / books I’ve read, that I think are important for anyone that would like to learn more on the subject:

• Understanding the PureMVC Open Source Framework by Ahmed Nuaman
• PureMVC: Implementation Idioms and Best Practices [PDF] by Cliff Hall
• Discovering PureMVC, and scaling the learning curve by Toby Ashley
• Building a Flash site using PureMVC by Yee Peng Chia
• Puremvc Tutorial – Flex, Puremvc, Jabber and Xiff 3 by Dave Keen
• Creating a YouTube Search and Play Gadget with PureMVC by Ahmed Nuaman
• Minimalist MVC example using the PureMVC Framework by Chandima Cumaranatunge
• ActionScript 3.0 Design Patterns: Object Oriented Programming Techniques [Book] by William Sander and Chandima Cumaranatunge

I’ll be keeping this list updated with new articles / tutorials / books once I find and read them.

Any feedback?

Do you use PureMVC or have tried it? Like it? Hate it? Maybe another framework?
I would love to hear your opinions and to know whether or not I should go for a “Round Two” article on the PureMVC subject.
Your feedback will be much appreciated!

For updates on more articles like this, subscribe the blog’s RSS Feed.

Photo by Jean Scheijen.

Decorreu no passado sábado, 14 de Novembro, o evento Upload – 2.0 meeting. Um evento de cariz nacional que juntou estudantes, profissionais e interessados nas áreas de Comunicação, Marketing e Relações Públicas para promover a discussão e interacção sobre a Web 2.0, a um custo acessível a muitas bolsas.

Atendendo aos assuntos discutidos no evento e ao facto de ter conseguido juntar mais de 250 participantes num espaço fechado, durante um dia inteiro (com pausas para almoço e coffee breaks, claro!) para ouvir 11 oradores e 3 moderadores — e tendo já lido algumas opiniões de participantes —, julgo ser seguro afirmar que o evento foi um sucesso.

Vou directo a um assunto que mais opiniões gerou e continua a gerar: o painel projectado da hashtag do evento no Twitter (#uploadlx) que esteve presente no palco.
De modo geral, veio acrescentar valor às apresentações que iam decorrendo no palco, transmitido em tempo real o feedback da audiência e complementando alguns conteúdos com mais informações. No entanto, por vezes deu-se largas à imaginação em demasia, revelando-se alguma imaturidade da plateia, tendo até roçado a falta de respeito pelo trabalho do orador.
Para efeitos de medição da receptividade do público a cada apresentação, terá funcionado lindamente:
- Quando o público estava interessado, haviam poucos tweets e eram, na maioria, complementares aos conteúdos em foco no momento;
- Quando o público perdia o interesse, os tweets disparavam em larga escala e nas mais diversas direcções!
Em próximas edições do evento, julgo que será benéfico os oradores terem acesso visual ao painel, de forma a receberem feedback e poderem reagir ao mesmo, tornando-se assim a experiência realmente interactiva.

Avanço agora para uma pequena revisão / análise de cada orador / apresentação.

Ricardo Teixeira: depois de uma abordagem pelos conceitos web 1.0 “find me” / 2.0 “join me” / 3.0 “follow me”, veio falar na relação entre marcas e consumidores na web. Mas talvez por ter sido o primeiro orador do evento, ou só pelo facto do meu cérebro estar a “meio gás” naquela altura, acabei por não ter dado a atenção devida ao valioso conhecimento partilhado. Shame on me!

Luís Rasquilha: bem humorado, bom comunicador e sempre “a 200″, expôs tendências no panorama actual da web. Cedo manifestou ser conhecedor do mercado onde se encontra, mas que também é o seu negócio e, como tal, nem toda a informação poderia ser revelada num evento público. Falando em tendências, logicamente a indústria do sexo / pornográfica tinha de vir à baila, e vários foram os exemplos apresentados onde esta tendência se encontra bem expressa. Acordou e cativou rapidamente toda a plateia.

Durante as perguntas e respostas deste painel, foi discutida a genuinidade e necessidade de transparência na utilização de redes sociais por marcas / instituições / organizações e afins.

Armando Alves: levou ao evento uma apresentação pragmática, bem estruturada e rica em conteúdo. Questionou a real utilidade de muita tecnologia utilizada como ferramenta de marketing, sem que exista uma ideia ou conceito sólido a suportá-la. Revelou preferir o conceito Web Social ao genérico Social Media. Por fim, falou na importância de definir métricas específicas por projecto / campanha de forma a avaliar o real sucesso da mesma.

Rodrigo Moita de Deus: trouxe ao evento um momento ao estilo stand-up comedy, para falar de marketing político na web. Apontou defeitos e soluções na comunicação política online. Entre bastante humor, transmitiu várias ideias passíveis de serem aplicadas não apenas à política, mas também às marcas / empresas em geral que pretendem presença / retorno da web.

Sérgio Bastos: com dados estatísticos e exemplos muito interessantes, especialmente para PME’s, devolveu uma apresentação com base em muita pesquisa. No entanto, a falta de qualidades de orador, fez com que perdesse a atenção de grande parte da plateia praticamente desde o início do discurso. Foi o primeiro orador após o almoço, e talvez este facto tenha também contribuído para a falta de atenção do público.

Filipe Carrera: saltou para a frente do palco, e acordou a plateia adormecida, arrancando aplausos pelo meio. Deu umas “pinceladas à impressionista” por exemplos de sucesso de produção de conteúdos / utilização de ferramentas na web 2.0. Depois da entrada triunfal, a apresentação esmoreceu e assim se manteve até ao final, mas nem por isso os conteúdos deixaram de ser interessantes.

Daniel Caeiro e Flávia Paluello: a representar a Torke e marketing de guerrilha. O Daniel demonstrou boa capacidade de comunicação, depressa cativando a atenção do público e aproveitando alguma técnica de guerrilha, infiltrou provocação entre os conteúdos. Falou da gestão da presença de marcas em Social Media (ou “xoxial media” como proferiu algumas vezes) e da necessidade de transparência na comunicação. Perdeu pontos junto da audiência ao mostrar, como exemplo do portfolio, a acção MySpace Portugal que roçou publicidade enganosa.

Fernando Baptista: relembrou o que é “ser social” e que a presença de marcas em redes sociais deve ser regida pelos mesmos princípios básicos das relações interpessoais. Da mesma forma reforçou a importância de marcas / empresas usarem várias agências (relações públicas, media, digital, etc), cada uma com um objectivo específico, e colocá-las em conversação sincronizada o mais cedo possível.

Vasco Trigo: depois de mais uma breve abordagem sobre a história do universo em geral e da internet em particular, fez uma passagem pelo futuro, definindo o conceito web 3.0 como “a web das coisas”. Falou de ética na produção de conteúdos online e da responsabilidade dos jornalistas na contribuição para um futuro mais semântico de modo a reforçar a autenticidade da informação disponível. Teve ainda tempo para uma chicotada política, pena o facto da audiência já estar reduzida nesta altura. Foi quase um Magazine 2001 / 2010 (RTP2) em directo, como foi referido várias vezes.

Paulo Querido: trouxe uma apresentação visualmente original. Falou da evolução da internet, com alguma “previsão” do futuro sobre o conceito web 3.0, sob o termo “web líquida”. Tendo sido a última apresentação do dia, foi prejudicado por vir repetir muita informação já discutida ao longo do dia e pela fraca assistência do público, que nesta fase já estava reduzido a cerca de metade. Foi dos poucos oradores que tentou interagir com o público lendo o feedback no painel do Twitter, acabando por ter de desistir a fim de não se perder na linha da sua apresentação. Demonstrou conhecimento e um trabalho consistente de pesquisa / preparação.

Nota final para a promoção de hábitos de leitura e partilha de conhecimento em papel, que a organização levou a cabo com a oferta de livros em “troca” de inscrições e ainda uma iniciativa de bookcrossing (troca de livros) entre os participantes. Ambas as iniciativas são de louvar, mas fica a sugestão de limitar o tema para bookcrossing, pois embora a variedade fosse muita, não interessava a todos os participantes, e assim no final alguns levaram de volta o livro que entregaram no início.

Reforço novamente a nota positiva que todo o evento merece. O sucesso do evento foi resultado da boa interacção entre todos os intervenientes.

Deste modo: parabéns à organização, oradores, moderadores e aos participantes!

P.S.: Agora… ficaram no ar duas questões: quando e onde será o próximo Upload?

Foto de Seegno.

Now fast-forwarding to last week.

Last week, reading my Twitter’s timeline, found a tweet of @Quodis, on welcoming their newest team member: @Leihla. Being a follower of Quodis‘ work and having some free time on my hands, I went to check on Leihla’s Twitter account to find out more about her. Suddenly, a simple hashtag got my full attention: #time on the following tweet “Tried the pomodoro technique and saw some improvements on my time management“.

* Ding! Ding! *

I had to find more on this “pomodoro technique”. And so I did: The Pomodoro Technique, the official website on the subject.

The Pomodoro Technique is a time management method, created in 1992 by Francesco Cirillo as a way to improve his own study habits. Since then it has been taught and practiced by professional individuals and teams all over the world.

The name Pomodoro, means tomato in italian, and it was adopted due to using a kitchen timer (tomato shaped) to keep track of the time.

The success of this technique relies on a few simple rules:
- work with your focus on a single task for 25 minutes (a Pomodoro unit — an indivisible time measurement unit);
- then take a 5 minute break;
- repeat the last two steps, until the task is finished and the active Pomodoro ended;
- every 4 Pomodoros take a longer break, like 30 minutes.

These are the basic rules, but there’s a lot more to add to it. For a deeper study, I recommend reading the Book (in PDF or printed version) available on the official site.

Right from the first day I started using this technique, results came up. Not only I enhanced my productivity, but also found a lot of interruptions I didn’t noticed they existed before (as interruptions / momentum breakers).

In fact, this system enables a lot more then just improving productivity, it increases awareness of decisions and determination to reach objectives, building motivation that will fuel more productivity.

In resume, it’s a methodology so simple, one can learn it in… well… a Pomodoro. (I had to pull this one off!)

As a final note, the set of tools I use to implement the Pomodoro Technique:
- Pomodoro Desktop, a free Mac status bar application to track time;
- The Hit List, a beta (free by now) release of a Mac application for task management.

Update:
An alternative desktop timer, platform independent (AIR-based), is Focus Booster.

So… feeling the need to take control of your productivity time?

Photo by Jacki-dee.

With Google announcing yesterday (28/10/2009) its Maps Navigation app for Android 2.0, all the major players in the GPS Navigation market felt the shockwave. Garmin’s shares dropped 16%, while TomTom went down by 21% (Garmin & TomTom @ Google Finance).

Google not only entered (probably) the most lucrative (and expensive) market of mobile apps delivering a free (!) app, but also managed to cook it in a feature-rich way. It takes advantage of running in an internet-enabled device (versus most GPS dedicated devices), backed up by the Google Search Engine big-brother-monster and adds more skilled and totally useful features like Search by Voice, Street View and Traffic View.

As an iPhone owner — not willing to get the all-new Motorola Droid — and for the sake of an healthy competition in this mobile GPS market, I hope Google and Apple settle their differences fast so that Google Maps Navigation app gets released in other phone flavors — at least Google said they’re “eagerly working” with Apple on it.

Let’s wait and see how this game evolves.

Photo by laihiu.

This will serve as an extension of my Twitter account. A base where I can publish my thoughts on particular subjects. From trending topics like social media and user interaction, to more boring ones like coding meta-patterns and usability.

If I got your attention, you can always stop by every other week to check what’s new, or follow me on Twitter, as I will certainly link back to any article I’ll post here.

Thanks for stopping by!

Photo by -staci-.