276 karma · joined May 4, 2009
https://github.com/joshtynjala https://twitter.com/joshtynjala https://feathersui.com https://logic.ly
https://github.com/material-components/material-components-w...
Again, this was probably 3-5 years ago, and older versions of Flash Player may have been less optimized. This may be one of the many optimizations they made to Flash Player after Apple decided it wasn't fast enough for iPhones.
Facebook could have done the same thing with their app too, so I don't see how this affects validity.
I may be over-thinking this, but in case you didn't know, Flash Player in Chrome is still developed mostly by Adobe. Chrome has a different plugin API, I think, and some extra sandboxing, but the core parts of Flash Player in all browsers come from the same Adobe-owned codebase, including Chrome's bundled version.
If you don't have those contacts, you need to speak up and get your name out there within the community where you want to find work. Blog about the technology you work with, and show off cool personal projects. Join a local user group. If there is group discussion at the meetings, show that you know your stuff. Go to conferences and make sure you find people to chat with during the day and later on when everyone goes out for dinner and/or drinks at night. In short, it's up to you to show and tell people how great you are before they'll want to work with you.
What's the point of including the speculation about the download numbers of the top three apps? Even if the top three publishers didn't want to share, maybe the author of the post could have gotten some more data from other top 30 publishers to make a more educated guess. The stats for one app can't magically result in the number 70,000. What are the other "observations" that are mentioned?
The author specifically talks about the big spike in downloads on Christmas day, but only the screenshot of the graph at the end shows the numbers after Christmas. They're dropping fast. When are those numbers going to level off? It would have been nice if the author waited a week before posting. At least then we could make better predictions about how well apps will do when everyone returns to their normal routine in the new year.
Finally, I wish that the post had included some data about paid apps. Was the spike on Christmas as dramatic for paid apps? We know that Android users are less likely to pay for apps overall than iOS users. Do Amazon Appstore users have the same behavior? If so, did the Kindle Fire Christmas gifts bring in new type of Android user that is more willing to fork over money for apps?
Source: http://www.adobe.com/devnet/flashplayer/articles/privacy_mod...
Local storage here refers to "Flash cookies".
Additionally, many Windows apps still use OK, Cancel, Apply buttons in settings dialogs. The instant saving of settings is more of a Mac thing. Users are going to expect similar things from UI on the web, and the majority are probably new to the idea of no save/cancel choice.
http://googlechromereleases.blogspot.com/2010/06/stable-chan... http://blog.chromium.org/2010/03/bringing-improved-support-f...
Is there any part of Logicly in particular that felt slow to you? Please note that signal propagation does intentionally limit the speed of the simulation at the moment. However, dragging objects around on the design canvas felt exactly the same to me when I tried it in both Logicly and QuickFuse in Flash Player 10.1 and Chrome 6 respectively.
The biggest slow-down is intentional, though. Since the wires are colored, propagation is currently limited to the frame rate so that all changes can be seen. Some circuits, like the oscillator sample, look pretty strange when propagation isn't tied to the frame rate. I plan to add a setting to turn off wire colors, and then I'll probably make the propagation adjustable too.
1. How do you set an initial state when controls are also interactive? This is probably easier to do now that I have a floating property editor window. At the time, all interactions with components were direct.
2. If something is interactive, like a switch, what's the best way to handle dragging it with the mouse? Previously, the "wall plate" of the switch was the only draggable part, but it didn't seem like the best choice for usability. Also, it limits the visual design because draggable areas must be large enough to be discovered. I've considered having an extra draggable handle appear when a component is selected, but I'm not sure if that's ideal.
Forcing a separation between a design perspective and the simulation made the answers obvious. However, now that you've made me explain my reasons, I can see that it might be possible to go back to the old way without sacrificing too much.