http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/ Fri, 18 May 2012 16:57:56 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-333 data recovery Fri, 04 Jun 2010 01:52:25 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-333 I love android phones but never used motorola so cant comment on its features. I love android phones but never used motorola so cant comment on its features.

]]> http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-171 Motoblur & Android Fragmentation: The Follow-Up | Volker on Mobile Tue, 13 Oct 2009 00:04:35 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-171 [...] I blogged about Motorola’s Motoblur UI, which adds an additional SDK for its specific APIs beyond the standard Android stacks. I reckoned [...] [...] I blogged about Motorola’s Motoblur UI, which adds an additional SDK for its specific APIs beyond the standard Android stacks. I reckoned [...]

]]> http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-250 tederf Mon, 12 Oct 2009 07:01:35 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-250 Sorry had a bad typo --- this is what I meant:<br>There will always be fragmentation but there needs to be good tools and compilers to alleviate a lot of the pain. But you fell into the "onerous internal and external QA" trap - too much crap out there already. Sorry had a bad typo — this is what I meant:
There will always be fragmentation but there needs to be good tools and compilers to alleviate a lot of the pain. But you fell into the “onerous internal and external QA” trap – too much crap out there already.

]]> http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-251 tederf Mon, 12 Oct 2009 06:58:25 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-251 There will always be fragmentation but there needs to be good tools and fragmention to alleviate a lot of the pain. But you fell into the "onerous internal and external QA" trap - too much crap out there already. There will always be fragmentation but there needs to be good tools and fragmention to alleviate a lot of the pain. But you fell into the “onerous internal and external QA” trap – too much crap out there already.

]]> http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-169 tederf Mon, 12 Oct 2009 02:01:35 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-169 Sorry had a bad typo --- this is what I meant:<br>There will always be fragmentation but there needs to be good tools and compilers to alleviate a lot of the pain. But you fell into the "onerous internal and external QA" trap - too much crap out there already. Sorry had a bad typo — this is what I meant:
There will always be fragmentation but there needs to be good tools and compilers to alleviate a lot of the pain. But you fell into the “onerous internal and external QA” trap – too much crap out there already.

]]> http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/comment-page-1/#comment-170 tederf Mon, 12 Oct 2009 01:58:25 +0000 http://vhirsch.com/blog/2009/10/12/more-fragmentation-android-motorolas-motoblur/#comment-170 There will always be fragmentation but there needs to be good tools and fragmention to alleviate a lot of the pain. But you fell into the "onerous internal and external QA" trap - too much crap out there already. There will always be fragmentation but there needs to be good tools and fragmention to alleviate a lot of the pain. But you fell into the “onerous internal and external QA” trap – too much crap out there already.

]]>