We open sourced Rebound for Android a few months ago. It provides simple spring dynamics similar to Pop and is used to drive animations in Facebook apps like Chat Heads and FB Home.
Very cool! Though I wasn't very clear I actually meant I'd like to see this made available via Maven Central as an aar, so that it could more easily be incorporated into Gradle based applications - though having a build.gradle makes it fairly trivial to pull the project and manage that oneself, especially now that Guava is no longer a dependency as well :)
Really awesome to see Facebook producing stuff like this.
Hi folks. I'm one of the engineers on Facebook Home (disclaimer these are my opinions and not those of Facebook). It's been really interesting reading the early reviews. I think we can learn a lot from them.
The goal of the product is to make your phone feel more alive with content from the people you care about while still allowing you to efficiently perform all the typical tasks you use your phone for. The navigation model is a bit different than what people have become accustomed to, so some confusion is very understandable; however, we tried very hard to make access to any task just as efficient on Home as any other launcher. Getting to any app is just one gesture away: swipe up to launcher; swipe right to the last app; or double tap the home button to bring up the switcher. As user feedback comes in we'll continue to tune our model to try and achieve a nice balance between surfacing social content and completing tasks.
Home was designed and engineered by a pretty small team with a goal of releasing a high quality, performant, and beautiful product. To ensure our bar was met, we tried to narrowly focus on doing just a few things but doing them well for the first release. Of course the trade off here is that some features that people value are missing. I hope this first version will be judged on the execution of what we did include as we continue to fill in the gaps in future releases.
For anyone who has checked it out so far Thank you! I'm looking forward to making the experience something you'll love.
I'm sure you've already received similar feedback; but still: pressing the home button for me is something that should never result in a spinner showing up for a few seconds. The first time I saw this I had to restrain myself from immediately deinstalling Facebook home (and that's coming from someone who decided to try out the app for at least a few days).
Furthermore I'm missing a way to show the currently showing post in the Facebook app (I want that because home is missing some features).
Finally: I was somewhat frustrated to learn upon release of Facebook home that you guys decided to start out us-only. Understandable of course, but please don't make the rest of the world wait in vain for the arrival of a date (the 12th) that doesn't actually allow you to try out the app (I sideloaded an apk instead).
On a more positive note: ballsy move, and nice execution!
Thanks for the feedback. I agree that hitting a loading spinner on the home screen should never happen. Sounds like you might have encountered a cold start. Occasionally the Android OS will kill our process to relieve memory pressure. This tends to happen when you are using an app that consumes a lot of memory in the foreground and then return to Home. Improving our cold start time and adding additional protections to our process to make it less likely to be killed are things we're working on. We're also continuing to tune our ranking algorithms for showing you the freshest most interesting content when you turn the screen on. The fullscreen experience of Cover Feed presents some unique and interesting technical problems to solve, but our goal is that the most relevant and fresh content is always given the highest priority. We'll continue to tune this over time and fill in missing features. We'll be making some blog posts about the engineering of Home soon that will go into more detail on some of these areas. Thanks for your patience on the wider rollout. I'm really excited to get this in the hands of more users.
I think overall the design and implementation is quite impressive. However, the feeling I got when I installed it last night was that it limits my phone's experience (ie., no widgets, etc). So while I can see Facebook Home appeal to hard-core FB users (ie., especially younger ones), I don't think it will appeal to everyone. But that's not necessarily a bad thing if the target is the hard-core FB user. I'm sure over time FB Home will get better and likely appeal to more people and it extends its capabilities.
Right on. Thanks for checking it out! I'm looking forward to getting more of the features that power users look for in the launcher so we can widen our potential audience.
The number one thing I noticed right away when I used Home for the first time is that it does not allow for direct swiping to camera.
This is the NUMBER ONE thing I use on my iPhone - as I need to get to camera ASAP in instances.
With the fact that FB owns instagram and the experience that home provides is a rich visual one - I hope this is one of the first updates you make.
(I know that the canned response may be: "well its easy to get to the camera by..." -- Sure, it may be easy - but its WAY TOO SLOW - get out of the way of the camera.)
I really love the look and feel of Facebook Home, great work on the overall design! I do think it's a bit awkward in how it handles my applications and the lack of widgets is a huge downer, but I'm sure you guys will figure that out.
That said, is there any chance the Facebook for Android app will be updated to be more like Facebook Home? It's incredible how much _better_ Home looks and feels on my phone. It's incredibly jarring when an action in Home opens the regular Facebook app.
How does it affect user's privacy? Play page says - THIS APPLICATION REQUIRES NO SPECIAL PERMISSIONS TO RUN.
That I don't understand this coming from Facebook, if this means Facebook isn't reading anything.
Though the app is not available in my country, a friend from US said it's plain clunky and he uninstalled it within minutes. My concern would be privacy, mostly because it's Facebook.
This is a really nice inventory of the latest Chrome Developer Tools. I also really like the recent Settings additions of "emulate touch events" and "Override device metrics" for mobile web development.
Bravo on making it work with WebGL! It's super smooth.
I see we both went with variable names like 'up' and 'left' for the subscripts in the "neighbor count" code. I'm always looking for ways to sidestep numerical array indexing because it's such a fertile ground for bugs. For example, I find it really hard to look at:
var up = i-1>0 ? -1 + i : -1 + h;
...and tell if it's correct. I used a mod_wrap function instead, which is an implementation of Python-like modulo, which 'wraps' negative numbers to the top of the range.
Thanks for the code review folks. I made the countNeighbors method a bit more concise and removed some unnecessary binding code from the travelWorld method.
I've been playing around with CoffeeScript and docco a bit lately and I thought I'd share this little project. Thanks to Jeremy Ashkenas for creating these fantastic tools.
http://facebook.github.io/rebound/rebound-js/docs/rebound.ht...