As we said in previous blog post we decided to use Objective-C to build a native iOS app. We have been working hard on the development and this is where we are so far : These are two screen shots taken from the progress made so far. We have a live map of Ireland that updates daily. It […]
Tag Archives: iPhone
TouchDevelop is a touch-friendly app creation environment for iPad, iPhone, Android, Windows, Mac, Linux.
TouchDevelop is a touch-friendly app creation environment for iPad, iPhone, Android, Windows, Mac, Linux developed with
While trying to recreate a currently native Android and IPhone app as a hybrid app (using React), I came to the point where everything was unacceptably slow. React’s diffing algorithm might be fast enough for many “normal” things, but it’s definitely too slow for doing animations (especially on mobile).
Another thing that bothered me, was that suddenly I had to put things in my state that didn’t really belong there, as they were not truly describing the application’s state, but solely some intermediate state, only needed for animation. This would mean that I could no longer easily serialize the applications state as it was cluttered with unnecessary state descriptions
On December 6th, a small conference on the topic of Functional Programming in Swift will take place in Brooklyn. We’re super-excited by the new possibilities and decided that it’d be great to spend a day talking about this with interested people. We’ll have some formal talks but also plenty of time and space for informal chats in between and after the talks.
- 10:00a – 11:00 : Coffee and morning reception
- 11:00 – 11:35 : Natasha Murashev
- 11:35 – 12:10p : Brian Gesiak
- 12:10p – 1:10 : Lunch
- 1:10 – 1:45 : Justin Spahr-Summers
- 1:45 – 2:20 : Andy Matuschak
- 2:20 – 2:50 : Break
- 2:50 – 3:25 : John Gallagher
- 3:25 – 4:00 : Brandon Williams
- 4:00 – 5:00 : Hang out and close up
- 5:00 – beyond : Hang out at a neighborhood spot
Product design and development can cover a range of devices and platforms: iPhone, iPad, Android phones and tablets, responsive web applications and web sites, desktop apps, and web-based prototypes… and if you work in a very large organization, you may have a range of products and features to add several variations or themes within each of these areas.
In order to stay productive and effective across teams, platforms, and devices, systemic design and development is imperative. UI Libraries and Style Guides are a great step towards keeping everything aligned. But how can this style guide be a maintainable, useful resource rather than a distraction?
Learn from a product designer’s perspective from past and current projects ranging from small teams to large enterprise teams — how she and her teams have strived to maintain a “single source of truth” for a truly living spec through a living style guide and prototype — all of which can improve your product design and development lifecycle.
Jina is a Senior Product Designer at Salesforce UX, where she helps design and develop systems and patterns across multiple teams within an enterprise company. She also loves Sass; she leads Team Sass Design, runs The Mixin (an SF-area Sass meet up), and helps Susy.
Part of a system I currently working on is manipulating raw data. The data being sent from multiple client devices(Android/Iphone devices, etc..) ~ 100,000 requests per day.
The raw data need to be collected and ready for later use. It gotta be searchable and aggregated for calculations.
I had little experience with Solr but this time I wanted to try ElasticSearch(ES). I read about ES out of the box clustering and shards capabilities so I gave it a shot.
The installation is simple and quick. ES ships with comfortable UI dashboard(Marvel) and a command line tool to execute queries.
After playing with the framework I created my first Index and Mapping types (MyIndex, MyType).
I didn`t know that point how exactly my data going to be structured so I went into “all-fields-querying’. Meaning that for a single input searching the ES engine will go through all documents and search in each document’s field. The matching documents will return.
We may achieve this by using the field _all. That field includes flatten text of one or more other fields within the document indexed. the field is populated by default (if enabled).
The query is pretty easy: