sghael

The convention should be to use 1337 as your seed, and disclose that in your publication.

Localytics | Boston | Front End, iOS, Android | ONSITE Localytics provides a mobile engagement platform for many of the world’s top app publishers including ESPN, Grindr, Periscope, and HBO. Our customers rely on us to keep their mobile users happy and engaged. We provide tools to drive great app experiences including push messaging, mobile analytics, predictive analytics, and individualized in-app experiences.

We are hiring front end engineers! We have a modern front end stack (ES6, React, Redux, Webpack) and a history of front end thought leadership and open source contributions.

We are also hiring mobile engineers with a focus on Android and iOS development. We build tools for our fellow mobile developers and write code that is deployed on billions of devices around the world.

To apply or learn more about either opportunity send an email to [email protected] Check out our engineering blog: eng.localytics.com

Also looking forward to the technical writeup.

Not sure if it's just me, but when touching the menu controller on the top left, the dom slide over to reveal... nothing. Also, general weirdness using the gear button to change selection between all/enqueues only/ratings only/reviews only. Selecting something other than all does nothing and doesn't persist.

I'm on Android 2.3.3. My Touch 4g slide. Stock browser.

The photo isn't store in a database. It's stored on S3. They are not backing up S3, so this concern is misplaced.

Could you give a little more detail on your setup? I'm curious how others are designing around these issues.

This is Sandeep (co-founder of Ravid). My co-founder (keithba) and I found that sending private, asynchronous video messages on mobile devices is way more difficult than it should be. We created Ravid to solve this problem.

Note: US-only for now & requires a phone (so no tablets.)

The stack & tools:

  * Rails 3 (MRI) for our API servers.  
  * Worker nodes running Sinatra (JRuby) w/ Resque
  * Monit for monitoring services / Fabric for quick provisioning
  * The Android client is typical Java (using IntelliJ)
  * iPhone development w/ Monotouch! 
  * S3 for storage, and our public website using Jekyll
  * C2DM message delivery (our Gem: https://github.com/sghael/speedy_c2dm)

Lessons learned so far:

- Fragmentation on Android is a b. Especially when dealing with hardware stuff like cameras, expect to do a lot of device specific coding. Front-facing cameras are a perfect example. Gingerbread solves these problems in theory, but not in practice.

- Uploading video files over mobile connection is non-trivial (duh) - We've put a lot of work towards reliable and efficient uploads and downloads (intelligent packetization, retry logic, etc). We solve for the "elevator scenario". User sends a message, but steps into an elevator half way through delivery. Aside from Gmail, most mobile apps suck at this.

- On the positive side, 4G+ speeds are really impressive.

- Creating a portrait oriented camera application for Android is way harder than it should be (really poor API implementation around camera rotations). Contrast to iOS where it's super easy.

- UX matters - A friction-free UX required a lot of work. We had many alpha testers (both family and friends & paid services like usertesting.com/mobile) that helped us find the sticking points.

We'd love your feedback on anything!

That seems like a non-sequitur. Based on the article, LightSquare isn't an application of GPS. It's a wireless broadband network that just (unfortunately) happens to f with GPS signals.