Mobile Dev Memo aims to be the most comprehensive resource for mobile app development. In addition to publishing regular content, Mobile Dev Memo aggregates content from across the web in the form of "memos", or descriptive article headlines capable of fomenting discussion.

What are Memos?

Memos are pieces of information retrieved from across the web. The memos are fetched intermittently throughout the day and then classified; if they fall into certain categories and fit the profile of something interesting and relevant to the mobile development community, they're posted to the front page and given a dedicated space on this site for discussion. This is an example of a memo.

How are memos collected and categorized?

Articles and user-generated content are retrieved periodically throughout the day from a defined set of sources. Each item retrieved is "memo-ized" and classified into categories (the category list can be found on the front page). The classification routined used on Mobile Dev Memo has been released as open source here.

Classified memos are then evaluated by a "relevancy engine" driven by Twitter data; if the memo is deemed relevant, it is published to the front page's stream. The most relevant memos (as deemed by the relevancy engine) are also published to the Mobile Dev Memo Twitter account.

The process by which memos are fetched, classified, and published is depicted below:


Who is behind Mobile Dev Memo?

Mobile Dev Memo is operated and curated by Eric Seufert. All images on the site were designed by Vladimir Šipka.

Posting job listings on Mobile Dev Memo

Visit the jobs page. Jobs are posted for 60 days; new submissions are included in the site's sidebar and indicated as "featured" on the jobs page (highlighted and kept at the top of the list) for the entirety of the job listing's lifetime.

Writing for Mobile Dev Memo

Article submissions to Mobile Dev Memo are welcome, so long as articles submitted meet the following criteria:

- The article should be relevant to all aspects of mobile software development and not germane exclusively to a particular vertical, eg. gaming. This doesn't mean that an article about a particular topic or breed of app won't be accepted; rather, it means that conclusions drawn from the article should be applicable to mobile app development in general.

- If the subject of the article is a current event (eg. a recent acquisition, a company's change in strategy, the release of a data point, etc.), the article should remain relevant long after the event has been forgotten. In other words, the article should be using the event as a case study, not merely reporting on it.

- The article should be written in English and be between 600 and 1,500 words in length.

Articles can be submitted either in their entirety or as proposals using the contact form.


The views expressed in original content published on Mobile Dev Memo or in content re-published on Mobile Dev Memo represent those of their authors and not necessarily the views of the employers of the authors. Articles ("memos") linked to in the Mobile Dev Memo feed have been fetched and categorized algorithmically; as such, the re-publishing of an article does not necessarily imply consent or approval for the views expressed in that article.

© 2012-2013 Mobile Dev Memo