mercredi 21 juillet 2010, par ReedR
The buzz around Windows Phone is getting pretty crazy. This past weekend, reviews and walk-throughs emerged on almost all of the major tech blogs. It’s about time. iPhone and Android have had their 15 minutes. Microsoft has been cooking something in the back room under lock and key and release is imminent. You have to wonder, will it sink or swim? Is it too little, too late?
The new kid is Windows Phone 7. He’s smart, he’s different, and brings much needed change to our mobile platform strategy. With change comes excitement and some trepidation for our legacy mobile developers. After all, this is a completely new platform-- not an upgrade from Windows Mobile in any way. What does it all mean?Windows Mobile and Beyond
Windows Mobile is still alive and well. It’s been the best mobile LOB platform around and continues to move forward under the ownership of our Embedded Team as Windows Embedded Handheld. It’s flexible, adaptable and comes in every variety of hardware you can imagine. When my A/C unit blew up last month, the service guy shows up with a high tech gadget. It was indestructible (e.g. – ruggedized). It was a two way walkie-talkie. It managed the work order for my house and captured my signature. It ran technical diagnostics on the data collected. It pumped the whole work order up into the cloud and then magically printed my receipt to a wireless Bluetooth printer on the tech’s belt. WM has a great device management story, meets most security requirements, and gets the work done.
Windows Mobile is a great LOB platform for many uses but it has struggled with non-geeks who buys smartphones (e.g. – average consumer). The same flexibility that makes it powerful and adaptable is also responsible for the lackluster reputation with this crowd. There are a LOT of devices, form factors, and operator/hardware customizations that end up in Windows Mobile phones. OEMs have great flexibility that allows them to build a $100 device or a $3000 device depending on what they put into it. There are minimum bar requirements, but they are vague. Simply put, a Blackjack II… is not an HD2… is not a Tilt… is not a, you get the idea. These phones can run many of the same applications. They are all Windows Mobile. They are provide very different experiences and sometimes bare very little resemblance to each other. In the Enterprise LOB space, this isn’t a big deal since many companies standardize on a ruggedized device or pick a handful of “approved” devices to support for corporate workers. There is also big part of the world that doesn’t fit this profile. To them, it is a big deal.
The consumers space is … different. While people will debate endlessly about the superiority of Android, iPhone, Palm, Blackberry, or Windows Mobile … the answer is bigger than the platform itself. I would argue that all these guys have made big contributions to get us where we are. The mobile ecosystem is a complex, collaborative and adversarial bakery going after a very big pie. We’ve all attacked it from different angles and it’s evolving at rapid pace. The mobile phone market is so much bigger than the PC market and carries so much potential, it’s staggering. Okay, maybe I’m, a little crazy but there are a lot of numbers to back up my madness. The networks keep getting better. The cloud is emerging. There is a generation that cares more about their phone than their PC (if they even have one). Things are falling in to place to truly let this market take flight. While I’m very optimistic about Windows Phone 7, I’m even more optimistic about the mobility as a market opportunity. I don’t think anyone has scraped the surface yet. Not even Apple.
Why Windows Phone 7 is different…
The blogosphere is full of reviews and details about the Windows Phone 7 platform. I won’t try to reiterate all those things here. I will point out a few that make this a compelling platform to me as a developer… a few of my favorite things
A simple, compelling device than anyone can use. It’s something the average consumer can truly love. There is nothing super-techie or complex about using Windows Phone 7. It’s a joy. Keep it simple. Thank you. This device will appeal to anyone and that makes it a very good platform for developers to easily reach the masses.
A single install that is accessible to everyone. Windows Phone 7 is one download. It magically pulls down everything you need to get started. If you have a paid SKU of Visual Studio, it plugs in all the parts to enable Windows Phone 7 development. If not, it installs an Express (a.k.a. – free) version of Visual Studio...with everything you need. Code away.
Silverlight and XNA. Silverlight and XNA finally give you everything needed to build astonishing user interfaces. Hello XAML. Goodbye simple, but ugly WinForms. There is no excuse for ugly apps now. Windows Phone 7 is based on SL3 so most Silverlight devs can jump right in. Better yet, the tools, books, and resources for SL3 have been out for a while so there is a lot of good content to leverage. XNA is interesting because it’s also the framework that has powered community games on XBOX and apps on Zune. While XNA dev across these platforms is not identical, it’s pretty close and sets developers up for multiple opportunities to leverage their gaming investment.
A Zune Phone? It’s no secret… the only thing that broke the hearts of Zune HD buyers was that it wasn’t a phone. Windows Phone 7 does Zune…. and more. If you buy one CD a month, then Zune Pass is for you. For a price less than one CD, you have access to a staggering library of music anytime you want it. Considering 10 DRM-free credits each month to keep whatever you want (it’s yours), it’s the best way to try and buy music.
Consistency in hardware and user experience. The bar for Windows Phone 7 hardware is high and rigidly set. This means every device will be a great device… for gaming, for apps, for everything this platform is designed to do. With WM, OEMs had a lot of leeway with hardware requirements to pick and choose. No more. These devices will rock.
The Cloud. People will debate what “the cloud” really represents to them, but it’s undeniable that the industry is shifting. I still think of myself as an old-school C++ guy, but I write most of my code in .NET. It makes me more productive. I remember being very skeptical when .NET emerged and then warming up… it was like someone sat down and thought through the problems developers were writing code to solve and built the APIs around it. C++ suddenly felt like stacking grains of sand instead of stacking blocks. Cloud computing will change the way we build apps, store, and access data. Windows Phone 7 is positioned to help you get there. As a developer, there are many changes that may initially make you scratch your head, and then realize… oh yeah, something bigger going on here.
Push Notifications. You have a to love a super simple technique to integrate devices, applications, and services with a dandy little URI.
Marketplace is a first class citizen. If you are a developer, it’s a great way to get your apps to people who want to buy them. If you are a shopper… impulse buying has never been better.
XBOX Live. This is an enormous, fiercely active community, and something we’ve been waiting on in the mobile world for some time.
Location APIs. I think it’s the most important aspect of mobile opportunity and now it just works… no wrestling the GPS on each device or triangulating cell towers. It just works. Connecting people with needs to services and apps based on their location.
No more 32MB virtual memory limit. The virtual memory monster is dead.
Windows Mobile to Windows Phone 7. How do I get there from here?
I’m doing a lot of calls Windows Mobile developers who are trying to get their heads around Windows Phone 7. How do we get there from here? The answer is too broad for this post, but I’ll try to summarize some key points below:
If you are developing native code, you need to get to .NET (Silverlight or XNA). Native applications are no longer supported so if you are doing deep integration work, there may not be a 1:1 port. Windows Phone 7 protects the user experience and this means tighter control over what 3rd party apps can touch and interact with. NETCF Windows Forms will need to be replaced by a UI developed in Silverlight or XNA.
Application deployment is through Windows Marketplace. In the Windows Mobile world, it’s an option. With Windows Phone 7, it’s the requirement. While this is a hurdle for some enterprise and LOB apps want to control the install and distribution channel, it’s a great story for developers who just want a single way to sell their app to end users.
Widgets are gone. Widgets were basically little web pages wrapped in a control to make them look and feel like a stand-alone app. Moving your Widget to either a web page in the cloud or an application that leverages a browser control is pretty straight forward.
Windows Phone 7 uses Isolated Storage, not the file system you are used to. The file system you are used to is gone…even to the point that SD cards become part of overall “storage” and are not independently accessible. Silverlight developers will feel right at home with Isolate Storage but it’s a different paradigm for legacy devs. Apps are sandboxed and protected from each other all the way down to the data underneath them. If you use multiple processes and share data between them, you may need to re-think the architecture.
SQLCE is not part of this release for developers. SQLCE was such a huge part of our WM story, it’s hard to imagine a Microsoft Phone without it. For many simple storage requirements, Isolated Storage works just fine. If you have deep dependencies on SQLCE or are doing replication with SQL, this can be a hurdle. There are replication and database implementations already showing up for use on Windows Phone 7 using Isolated Storage to take the place of SQLCE short term. More to come on this one…
No more RAPI. If you have an application today that interacts with the desktop via cradled connection and RAPI, consider using the cloud or push notifications as a conduit.
Raw Sockets and custom connectivity over Bluetooth are not available. While the .NET libraries provide support for various connectivity scenarios, there is no low level support for raw sockets. Bluetooth support is limited to what the platform and UI provides out of the box.
No more background apps and services. This topic really stirs people up but it’s not a technical limitation…it’s a business one. If you want a great device experience, you have to lay down some ground rules to prevent the abuse of resources and ensure that devices stays “snappy”. The simple way to do this is giving the foreground app all the love. Background apps can still get notifications and interact with the user if something important needs to happen, but they don’t have free reign of the system like they used to.
You might be able to re-use more than you think. Remember when you learned how to go from desktop .NET to NETCF and things were very similar, but not everything was 1:1? Moving to WP7 is kind of like that. Expect to be able to re-use much of the private code and application logic you have written, but not all of the NETCF libraries are going to be 1:1. For example
If your company has rigid requirements for device control and management, you will need to re-evaluate what is supported with Window Phone out of the gate. While WP7 will support many Exchange policies (e.g. – PIN enforcement, remote wipe, etc.) it’s a new platform that is inherently different from Windows Mobile. Some of the deep device management tools you use today may not be compatible with WP7.
The legacy WM developers who are most impacted by changes to WP7 are going to be enterprise LOB developers and integrators who did a lot of low level work on Windows Mobile. If you can think outside the box a bit, WP7 may create new opportunities to do things you never could before. If you are struggling with what LOB might look like on WP7 or how to overcome some of the data synchronization you were previously doing for disconnected clients, I would encourage you to start with Rob Tiffany’s session on WP7 LOB.
Sum it up already…
Windows Phone 7 is a brand new foray into phones that enable every day people. If you are new to mobile development, it’s a good time to get in. If you are already a mobile developer (on any platform), it’s a refreshing new way to expand your reach and broaden your market. Never has the learning curve been so small for an opportunity this big.
-Reed
lundi 19 juillet 2010, par pierreca
Pas de lancement de plateforme mobile sans un concours – c’est quasiment devenue une institution pour encourager les développeurs à créer des applications… Windows Phone 7 n’échappe pas à la règle. Sur ce concours, nous voulons donner un maximum de visibilité aux applications qui seront créées d’ici le lancement et particulièrement de la visibilité face aux investisseurs… et pas des petits noms: Steve Ballmer, Antoine Granjon (Vente-privée.com), Ouriel Ohayon (AppsFire et le fond Isai), Marc Simoncini (Meetic et le fond Jaina), Bruno Vanryb (Avanquest) et Pierre-Olivier Carles (Kipost et Labotec)….
Mais avant de vous offrir 2 minutes pour les convaincre, et vous payer une visibilité de malade, il faudra se faire sélectionner parmi tous les concurrents à travers le nombre de “like” sur la page Facebook developpeurs de la vidéo de votre application.
Donc au boulot, tout est expliqué sur cette page!
Et pour ceux qui veulent tester leur application sur des terminaux, contactez-moi :)
lundi 19 juillet 2010, par pierreca
Pas de lancement de plateforme mobile sans un concours – c’est quasiment devenue une institution pour encourager les développeurs à créer des applications… Windows Phone 7 n’échappe pas à la règle. Sur ce concours, nous voulons donner un maximum de visibilité aux applications qui seront créées d’ici le lancement et particulièrement de la visibilité face aux investisseurs… et pas des petits noms: Steve Ballmer, Antoine Granjon (Vente-privée.com), Ouriel Ohayon (AppsFire et le fond Isai), Marc Simoncini (Meetic et le fond Jaina), Bruno Vanryb (Avanquest) et Pierre-Olivier Carles (Kipost et Labotec)….
Mais avant de vous offrir 2 minutes pour les convaincre, et vous payer une visibilité de malade, il faudra se faire sélectionner parmi tous les concurrents à travers le nombre de “like” sur la page Facebook developpeurs de la vidéo de votre application.
Donc au boulot, tout est expliqué sur cette page!
Et pour ceux qui veulent tester leur application sur des terminaux, contactez-moi :)
lundi 19 juillet 2010, par pierreca
Pas de lancement de plateforme mobile sans un concours – c’est quasiment devenue une institution pour encourager les développeurs à créer des applications… Windows Phone 7 n’échappe pas à la règle. Sur ce concours, nous voulons donner un maximum de visibilité aux applications qui seront créées d’ici le lancement et particulièrement de la visibilité face aux investisseurs… et pas des petits noms: Steve Ballmer, Antoine Granjon (Vente-privée.com), Ouriel Ohayon (AppsFire et le fond Isai), Marc Simoncini (Meetic et le fond Jaina), Bruno Vanryb (Avanquest) et Pierre-Olivier Carles (Kipost et Labotec)….
Mais avant de vous offrir 2 minutes pour les convaincre, et vous payer une visibilité de malade, il faudra se faire sélectionner parmi tous les concurrents à travers le nombre de “like” sur la page Facebook developpeurs de la vidéo de votre application.
Donc au boulot, tout est expliqué sur cette page!
Et pour ceux qui veulent tester leur application sur des terminaux, contactez-moi :)
lundi 19 juillet 2010, par pierreca
Pas de lancement de plateforme mobile sans un concours – c’est quasiment devenue une institution pour encourager les développeurs à créer des applications… Windows Phone 7 n’échappe pas à la règle. Sur ce concours, nous voulons donner un maximum de visibilité aux applications qui seront créées d’ici le lancement et particulièrement de la visibilité face aux investisseurs… et pas des petits noms: Steve Ballmer, Antoine Granjon (Vente-privée.com), Ouriel Ohayon (AppsFire et le fond Isai), Marc Simoncini (Meetic et le fond Jaina), Bruno Vanryb (Avanquest) et Pierre-Olivier Carles (Kipost et Labotec)….
Mais avant de vous offrir 2 minutes pour les convaincre, et vous payer une visibilité de malade, il faudra se faire sélectionner parmi tous les concurrents à travers le nombre de “like” sur la page Facebook developpeurs de la vidéo de votre application.
Donc au boulot, tout est expliqué sur cette page!
Et pour ceux qui veulent tester leur application sur des terminaux, contactez-moi :)
lundi 19 juillet 2010, par pierreca
Pas de lancement de plateforme mobile sans un concours – c’est quasiment devenue une institution pour encourager les développeurs à créer des applications… Windows Phone 7 n’échappe pas à la règle. Sur ce concours, nous voulons donner un maximum de visibilité aux applications qui seront créées d’ici le lancement et particulièrement de la visibilité face aux investisseurs… et pas des petits noms: Steve Ballmer, Antoine Granjon (Vente-privée.com), Ouriel Ohayon (AppsFire et le fond Isai), Marc Simoncini (Meetic et le fond Jaina), Bruno Vanryb (Avanquest) et Pierre-Olivier Carles (Kipost et Labotec)….
Mais avant de vous offrir 2 minutes pour les convaincre, et vous payer une visibilité de malade, il faudra se faire sélectionner parmi tous les concurrents à travers le nombre de “like” sur la page Facebook developpeurs de la vidéo de votre application.
Donc au boulot, tout est expliqué sur cette page!
Et pour ceux qui veulent tester leur application sur des terminaux, contactez-moi :)
lundi 19 juillet 2010, par Terry Myerson
I’m very excited to share with this blog community, that our Windows Phone engineering team has hit a very meaningful milestone; one that we’re calling technical preview. We are certainly not done yet – but the craftsmen (and women) of our team have signed off that our software is now ready for the hands-on everyday use of a broad set of consumers around the world – and we’re looking forward to their feedback in the coming weeks, so that we can finish the best Windows Phone release ever together.
Before release of this milestone, the software has undergone extensive testing – in daily use by more than 1000 people at Microsoft who have been using WP7 as their only phone for the past several months, and the more than 10,000 devices in our test labs. We’ve been testing usability, battery life, network connectivity, and many other metrics for a long time. As a result of that work, I hope you will find the experience to be of surprisingly high quality.
Starting today, thousands of prototype phones from Asus, LG and Samsung are making their way into the hands of developers over the next few weeks. Combine that with the beta release of the Windows Phone developer tools, and I can’t wait to see how our developer partners take advantage of our new approach to smart design and integrated mobile experiences. I’m personally working on a flash card app for my daughter, and am consistently amazed by the ease with which Silverlight and Visual Studio make WP7 apps possible.
So we’re almost there – but there is much work left to do. Together, with our early adopter customers, developers, OEM, and mobile operator partners we are in the home stretch. We are on the path to do exactly what we set out to do – create a different take on mobile phone software, an experience we think many people will find fun and refreshing, with a quality bar that we’re proud of.
I look forward to celebrating the release of Windows Phone 7 with all of you,
CVP, Windows Phone Engineering
dimanche 18 juillet 2010, par Long Zheng
It looks like Microsoft is not just making the Windows Phone 7 application development experience easy for developers, but it turns out designers have most of their job cut out for them. If you need to mock up an application UI for Windows Phone 7, it’s now as easy as mashing up some Photoshop files from the “Design Templates for Windows Phone 7″ resource.
Since finding useful information on MSDN is practically a treasure hunt, this 88MB archive is a treasure chest full of PSDs with layer-licking goodness. The gems include a full suite of UI controls as well as other practical UI elements such as the on-screen keyboard, notifications and start menu for easy drag and drop manipulation, if you can find the right layer amongst hundreds that is.
Although UI mockups are not impossible from scratch (especially if most elements are solid shaped squares), what I really like about this is that Microsoft is providing an official resource that will make mockups that much more consistent if not pixel-perfect with their real counterparts.
As someone who’s put together their fair share of mockups, trust me when I say this is awesome.
mardi 13 juillet 2010, par Long Zheng
At the Microsoft Worldwide Partners Conference 2010 yesterday, the Windows Phone 7 team took the opportunity to announce the beta release of its developer tools, another significant milestone for the platform as it inches closer to consumer availability.
As expected, this release includes an updated version of the emulator image (build 6414) for developers to debug with. Naturally, it took devoted xdadevelopers members no more than a couple hours to unlock some of its hidden glory. I recorded this thorough screencast video to save you the hassle.
Right off the bat you’ll notice performance and responsiveness has been improved several folds. Although some of that might be attributed to improvements in hardware acceleration for the emulator itself, I’m sure for the most part this is also the result of the optimizations the team has been doing in the recent months.
Diving into the every application and setting reveals the team has applied a very generous layer of polish throughout the OS, removing all traces of previously incomplete or inconsistent UI elements. For everything that do work, which excludes the social integration, email, games, Zune and Marketplace, it looks and works great. (Maps broke in the demo, but works great otherwise)
Finally, perhaps as a testament to just how close this release to manufacturing this code might be, some ringtones and alert sounds are in! Whilst I assume there will be more coming, the sound is quite unique and almost soothingly calm in a nice way. “Two Step” would be my favourite so far.
jeudi 8 juillet 2010, par Justin Garrison
Interested in Android but think you need to buy a new phone to try it out? Actually, your Windows Mobile phone may already have the capability of running Android. Today we show you how and the type of phone you’ll need.
![sshot-2010-07-07-[22-09-07]](local/cache-vignettes/L300xH96/sshot2010070b55e-ca43c.jpg "sshot-2010-07-07-[22-09-07]")
Installing Android
To run Android you will need a microSD card that is not SDHC (typically a card less than 2GB) and a supported Windows Mobile phone (see below). You can check your microSD card compatibility by looking at the card to see if it shows the “HC” label.
The microSD card will need to be formatted in FAT32. Plug the microSD card into the computer and right click on it and choose format.
Note: Formatting a microSD drive will erase everything on that drive. Make sure you have any important files backed up before you format it.
Now that the microSD card is formatted, the first step to installing Android is finding the right Android port for your phone (see below). You will need to find the port that works on your phone as well as the version of Android you want to run. Versions start at 1.0 but typically you will find ports for version 1.6 or 2.1.
Once you have found the right port for your phone and Android version you want to use, extract the files to a folder using 7-zip.
After the files have extracted there should be a folder called “andboot”. Go into the andboot folder and there will be another folder called “startup config” or “startup”. Open this folder and you will need to find the right startup.txt file for your phone. Inside each folder will be a single “startup.txt” file. Copy the file for your phone model to the root of the andboot folder. This file will tell Android what type of hardware you have, how big your screen is, how much RAM your phone has etc. so it is very important to choose the right file. If you are confused on what these phone names are please read below on finding your phone model.
Once you have moved the correct startup.txt file to the andboot folder, copy the entire andboot folder to the root of your newly formatted microSD card.
Plug the microSD card back in the phone and open the file browser on your phone and browse to the memory card. Make sure the phone is plugged into power before the next few steps because on some phones running on battery may cause the phone to hang.
Open the andboot folder and run haret.exe. If the right startup.txt file is in the root of the andboot folder you should be able to click “Run” and you will get a quick loading screen while haret turns off Windows Mobile and starts up Android.
You should get some scrolling text and probably a nice Android logo while the phone boots up the first time.
Note: The first boot is going to take a considerably longer time than subsequent boots. and you may need to calibrate your screen during the boot process so make sure you keep an eye on it.
Once the basic Linux settings are done your new “Android” phone will boot to a welcome screen so you can walk through the rest of the settings like setting up your email account.
Tip: If you are running Android on a phone that does not have an active data plan but does have wifi, you can get around the startup screen by tapping on the welcome screen in this order: top left corner, top right corner, bottom right corner, bottom left corner then tap the Android logo. You can then enable wifi and join a network and set up your gmail account manually.
It is usually recommended that you leave your phone alone while it syncs your information for at least 10 minutes. Once the initial syncing is done the phone should start running faster and you can play around with installing apps. If you don’t wait for the phone to fully sync you may have problems with apps crashing prematurely and a force close dialog popping up.
Change any settings and install any apps you want, they will be saved to your memory card and ready on next boot. All phones that run Android from the microSD card will automatically boot Windows Mobile when the phone restarts. To run Android again, just open the file browser and run haret.exe again.
Android Ports
There are a few different Android ports for Windows Mobile devices and each one supports a different family of device; each family of device has a varying amount of hardware support. Most phones will support the touch screen, hardware buttons, cell phone radio, and data connection, but some ports may not support bluetooth, GPS, or power management. This is not a complete list of Android ports available, but it should cover the most popular Windows Mobile phones.
Almost all Android development on Windows Mobile phones started with the development on theHTC Touch (also known as the HTC Vogue and the Verizon xv6900). The HTC Touch has 100% of the hardware features working and even some features that were not available in official Windows Mobile ROMs. One of the main differences between Android for the Touch and Android for every other phone is the Touch allows for Android to be flashed to the phone’s ROM (NAND memory). This was a big break through for Android development and has increased battery life and speed greatly. Running Android on the Touch can be done following the steps above but it is recommended to run Android by flashing the phones NAND memory. To learn how to do that, start at the Android Touch FAQ thread at XDA-Developers.Android ports for the HTC Touch can also be used on the following phones with varying success.- HTC Nike (Neon)
- HTC Polaris (Touch Cruise)
- HTC Kaiser (TyTN II)
- HTC Titan (Mogul, xv6800)
Note: HTC phones all have proper names that come from HTC and in many cases each carrier will give the phone its own branding and rename the phone to something else. For example, the HTC Titan was called the Mogul on Sprint and the xv6800 on Verizon. To find the Android port for your phone, start by finding the proper HTC name of your device. Start on HTC’s site to discover your device’s official name.
XDAndroid supports the most popular touch screen HTC Windows Mobile phones and if you bought a touch screen HTC Windows Mobile phone within the past year, most likely this port will support your phone. XDAndroid runs directly from the phones microSD memory card on the following phones:- Touch Pro (Fuze, RAPH, RAPH800, RAPH500)
- Touch Diamond (DIAMOND, DIAM500)
- Touch HD (BLACKSTONE)
- GSM Touch Pro2 (TILT2,RHODIUM, RHOD400, RHOD500)
- GSM Touch Diamond2 (TOPAZ)
Andromnia is an Android port for Samsung devices. Currently this port is in the pre-alpha stages and things like the headset speaker does not work. But if you want to test it out it supports the following phones:- Samsung i900 (GSM, supported worldwide)
- Samsung i910 (CDMA, used by Verizon in the US)
- Samsung i780 (Mirage)
- Samsung i907 (AT&T Epix)
Wing Linux isn’t as quickly developed as XDAndroid but should get the job done if your phone isn’t supported by any other port. Wing Linux supports the following phones to varying degrees:
- HTC Artemis
- HTC Elf, HTC Elfin
- HTC Excalibur, T-Mobile Dash
- HTC Gene, HTC P3400
- HTC Herald, T-Mobile Wing
- HTC Opal, HTC Touch Viva
- HTC Pharos
- HTC Prophet
- HTC Startrek
- HTC Wizard
- Asus P320, Galaxi Mini
You may also want to look at threads for the following phones to check the status of Android on these phones.
Extra links
If you still can’t find what you are looking for I recommend checking out these links for more information.
Similar Articles Productive Geek Tips Latest Software Reviews Tinyhacker Random Tips
Sur le Web
- > Savoir-Faire > Web > Google > Actualités Google
- > Actualités > Actualités du web
