Langsung ke konten utama

History Android ~ DroidUMM

Oleh
I’ve mentioned in previous posts that I’m a sucker for a kind word an even bigger one for a good infographic. I honestly, can’t get enough of them. Combine that with my favorite mobile OS and you have some info-gold on your hands. That’s what these guys from xCube Labs did when they managed to compile the history of Android into this awesome yet, informative infograph for you to enjoy. So whether you’re new to Android or a need to brush up on your history, it’s always good to know where you came from. (Might need to click the pic a few times to get the original size.) [Read More]



Label:

Komentar

Posting Komentar

Postingan populer dari blog ini

WhatsAppSniffer Hack WhatsApp

Oleh
Who uses WhatsApp Messenger? From The look of the  Play Store listing , a  damn lot  of people. Considering it's so popular, it's probably a pretty secure app, right? Think again. WhatsApp actually sends all chats in  plaintext , so anyone on the same Wi-Fi network can easily pull your entire conversation - including pictures and videos - straight out of the air. And now, that process is even easier than ever thanks to a new app called  WhatsAppSniffer . It's basically just a packet sniffer, but it makes the process of pulling WhatsApp chats out of the sky stupid-easy, and that's never a good thing. You might as well just shout your private conversations across the room.
12 komentar
Read More »

[Concept] Model View Present (MVP) Pattern for Architecture Android~ DroidUMM

Oleh
 Model-View-Presenter (MVP) is an architecture pattern for the presentation layer of software applications. The pattern was originally developed at Taligent in 1990s and first was implemented in C++ and Java. In MVP, the View and the Model are neatly separated and the View exposes a contract through which the Presenter access the portion of View that is dependent on the rest of the system.  [Next Article Implement MVP on Android] The Model is the component which preserves data, state and business logic; it just exposes a group of service interfaces to Presenter and hides the internal details. The View is the user interface, it receives user’s action and contract to Presenter to achieve user’s need, and then the View responds user by result information. The Presenter sits in between the View and the Model; it receives input from the View and passes commands down to the Model. It then gets result and updates the View trough the contracted View interface.
7 komentar
Read More »