{"id":3502,"date":"2014-06-13T10:00:48","date_gmt":"2014-06-13T14:00:48","guid":{"rendered":"http:\/\/me-en.kaspersky.com\/blog\/?p=3502"},"modified":"2020-02-26T18:58:43","modified_gmt":"2020-02-26T14:58:43","slug":"ios-tizen","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/ios-tizen\/3502\/","title":{"rendered":"Are New Smartphone Operating Systems Safe?"},"content":{"rendered":"<p>Practically simultaneously, Apple presented a new software update for its mobile operating system \u2013 <a href=\"https:\/\/business.kaspersky.com\/ios-8-arrives-security-consequences\/\" target=\"_blank\" rel=\"noopener nofollow\">iOS 8<\/a> \u2013 while its main competitor, Samsung, underlined the seriousness of its <a href=\"http:\/\/www.pcmag.com\/article2\/0,2817,2458822,00.asp\" target=\"_blank\" rel=\"noopener nofollow\">intentions<\/a> in promoting devices based on the new Tizen OS. Meanwhile, Google and its Android were out of the picture \u2013 out having a smoke or something like that. But despite the mobile elephant being absent from the newsroom, there\u2019s still plenty to talk about here.<\/p>\n<p style=\"text-align: center\">\u00a0<a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05111341\/safeos-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-5094\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05111341\/safeos-1.png\" alt=\"safeos\" width=\"640\" height=\"480\"><\/a><\/p>\n<h2><\/h2>\n<h2>Apple\u2019s new iOS<\/h2>\n<p>What seems most significant here is the clear drift towards more <em>openness<\/em> and <em>customization<\/em>. Completely unexpectedly, Apple decided to allow third-party developers (i) to replace the standard Apple on-screen input keyboard; (ii) to use the Touch ID interface; (iii) to integrate their widgets with the Notification Center; (iv) to broaden the types of data that can be exchanged between apps (including whole APIs for developers of certain <a href=\"http:\/\/9to5mac.com\/2014\/06\/02\/apple-announces-homekit-api-for-ios-will-serve-as-a-central-hub-for-home-automation\/\" target=\"_blank\" rel=\"noopener nofollow\">home<\/a> and <a href=\"https:\/\/developer.apple.com\/healthkit\/\" target=\"_blank\" rel=\"noopener nofollow\">health<\/a> apps); and a lot more besides.<a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05102541\/ios8-extensions.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-5095\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05102541\/ios8-extensions.png\" alt=\"ios8-extensions\" width=\"640\" height=\"382\"><\/a><\/p>\n<p>\u00a0<\/p>\n<p>All this had to happen sooner or later. After all, competing with the global developer community on OS development is hardly easy. The only way forward was to become more flexible. Just you watch: In a couple of years, Safari may lose its monopoly on default browser status. And that\u2019s not my imagination running wild \u2013 for who could have foreseen the change of mood re: an external keyboard?<\/p>\n<p>Against a backdrop of traditional howls of approval from Apple fans, the opposition didn\u2019t seem to even grumble, despite all sorts of interesting materials that came to light quickly in reaction. Examples: ZDNet published a curious <a href=\"http:\/\/www.zdnet.com\/apples-new-ios-8-openness-brings-new-security-threats-7000030146\/\" target=\"_blank\" rel=\"noopener nofollow\">analysis<\/a> of the new features\u2019 impact on security \u2013 due to a widening of the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Attack_surface\" target=\"_blank\" rel=\"noopener nofollow\">attack surface<\/a>. And Ars Technica quickly came up with a <a href=\"http:\/\/arstechnica.com\/gadgets\/2014\/06\/great-artists-steal-the-ios-8-features-inspired-by-android\/\" target=\"_blank\" rel=\"noopener nofollow\">comparison<\/a> of the \u2018new\u2019 features with various Android features, leaving the reader with serious doubts as to any genuine innovation from the guys in <a href=\"https:\/\/en.wikipedia.org\/wiki\/Cupertino,_California\" target=\"_blank\" rel=\"noopener nofollow\">Cupertino<\/a>. All the same, despite this, absent were cries of \u201cWhat the\u2026??? With Jobs still around there\u2019d have never been any of this!\u201d<\/p>\n<p>So, let\u2019s look at how Apple can hold on to the reins and maintain security. The system of pre-moderation of apps will remain, but still there\u2019ll be more for the Applers to keep on top of in terms of malicious functionality. The new <a href=\"https:\/\/en.wikipedia.org\/wiki\/Swift_(Apple_programming_language)\" target=\"_blank\" rel=\"noopener nofollow\">Swift<\/a> programming language seems to rule out a lot of developer mistakes early on in app development; however, Swift won\u2019t be the only \u2013 mandatory \u2013 development environment (yes: \u2018Seeking Swift programmers with a minimum of three years\u2019 experience\u2019). I\u2019m still of Eugene Kaspersky\u2019s <a href=\"https:\/\/eugene.kaspersky.com\/2012\/05\/31\/when-will-apple-get-security-religion\/\" target=\"_blank\" rel=\"noopener\">opinion<\/a> that Apple still needs to change its approach to security.<\/p>\n<h2>Tizen<\/h2>\n<p>Tizen. Tizen? Who the flip is Tizen?! For those who can\u2019t be bothered to get to <span style=\"text-decoration: line-through\">the library<\/span> <a href=\"https:\/\/en.wikipedia.org\/wiki\/Tizen\" target=\"_blank\" rel=\"noopener nofollow\">Wikipedia<\/a>, briefly, Tizen is Android\u2019s half-brother, whose stepdad is Linux \u2013 or something like that.<\/p>\n<p style=\"text-align: center\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05102540\/samsung-z480.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-5096\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05102540\/samsung-z480.jpg\" alt=\"samsung-z480\" width=\"640\" height=\"480\"><\/a><\/p>\n<p>\u00a0<\/p>\n<p>I\u2019m still not clear on concrete <em>technical<\/em> reasons for the creation of this OS. By that I mean: What\u2019s in it that isn\u2019t already in Android? It seems that they created it:<\/p>\n<ul>\n<li>to depend less on Google;<\/li>\n<li>to grab the biggest chunk of data, traffic and other valuable non-personified information about users;<\/li>\n<li>to be freer in how they choose their objectives and how to reach them. On the other hand, Tizen won\u2019t only solve the problem of Android\u2019s fragmentation (read: hotch potch of versions), but will also inherit all the inborn flaws of all projects of collective creativity \u2013 when each participant will be trying to get the biggest part of the pie for themselves (there are already as many as 10 <a href=\"https:\/\/www.tizenassociation.org\/members\/\" target=\"_blank\" rel=\"noopener nofollow\">main sponsors<\/a> of Tizen).<\/li>\n<\/ul>\n<p>Even more contradictory is the position of Samsung. It had its closed <a href=\"https:\/\/en.wikipedia.org\/wiki\/Bada\" target=\"_blank\" rel=\"noopener nofollow\">Bada<\/a> OS, which was coming on just nicely (in 2012 it surpassed the popularity of Windows Phone) and it could easily have created an ecosystem around it not unlike Apple\u2019s \u2013 only without Apple\u2019s flaws. Now it seems Samsung has started over (including a move to the new Tizen Store and spending millions on developers stimulation), and now it\u2019s got a load of competitors on board!<\/p>\n<p>Is Tizen the start of the end for Android? Will Tizen push Android off the devices of its sponsors?\u00a0<\/p><blockquote class=\"twitter-pullquote\"><p>Is Tizen the start of the end for Android? Will Tizen push Android off the devices of its sponsors?<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2FY72Y&amp;text=Is+Tizen+the+start+of+the+end+for+Android%3F+Will+Tizen+push+Android+off+the+devices+of+its+sponsors%3F\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>Probably no and no.<\/p>\n<p>Tizen, most likely, will do okay only in household appliances where dynamic development of features is not as important as stability, low fragmentation, and the possibility to develop the platform oneself. Open source code enables an extensive vulnerability checking \u2015 that is good for users (if Samsung &amp; Co. will be able to deliver patches quickly).<\/p>\n<p>Android will remain the predominant OS on smartphones and tablets; what\u2019s more, it\u2019s wholly believable that Tizen will see its share in this market fall to zero \u2013 unless it puts titanic efforts into the development of a good ecosystem (apps, app store, developer community, etc.), and this, as we\u2019ve seen with Microsoft and its Windows Phone, is no easy feat \u2013 even for very big companies. And while converting apps from Android to Tizen is rather straightforward (btw, just recently we showed off the beta of our new <a href=\"https:\/\/www.kaspersky.com\/android-security\" target=\"_blank\" rel=\"noopener nofollow\">antivirus<\/a> at the <a href=\"https:\/\/www.tizen.org\/events\/tizen-developer-conference\/2014\" target=\"_blank\" rel=\"noopener nofollow\">Tizen Developer Conference 2014<\/a>), it will only become a mass movement if it\u2019s totally worth the bother for everyone on the supply side.<\/p>\n<p>So what about Google?<\/p>\n<p>Google doesn\u2019t give a monkey\u2019s ____ about all this fuss. Android continues to <a href=\"http:\/\/www.kantarworldpanel.com\/smartphone-os-market-share\/intro\" target=\"_blank\" rel=\"noopener nofollow\">dominate<\/a> the market in terms of the number of sold devices, and has already caught up with iOS on <a href=\"http:\/\/www.netmarketshare.com\/operating-system-market-share.aspx?qprid=9&amp;qpcustomb=1&amp;qpsp=161&amp;qpnp=24&amp;qptimeframe=M\" target=\"_blank\" rel=\"noopener nofollow\">generated traffic<\/a> volume. Therefore, Eugene\u2019s <a href=\"https:\/\/eugene.kaspersky.com\/2010\/12\/07\/mobile-os-market-my-bet\/\" target=\"_blank\" rel=\"noopener\">bet<\/a> still looks safe J.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How iOS 8 and Tizen releases affect smartphone market and security landscape. <\/p>\n","protected":false},"author":188,"featured_media":3503,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[105,14,1061,543,440,44,674],"class_list":{"0":"post-3502","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-android","9":"tag-apple","10":"tag-ios","11":"tag-news-2","12":"tag-samsung","13":"tag-smartphone","14":"tag-tizen"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/ios-tizen\/3502\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/ios-tizen\/3605\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/ios-tizen\/3941\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/ios-tizen\/4159\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/ios-tizen\/3650\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/ios-tizen\/4013\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/ios-tizen\/4316\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/ios-tizen\/5093\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/ios-tizen\/3378\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/ios-tizen\/3938\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/ios-tizen\/4316\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/ios-tizen\/5093\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/ios-tizen\/5093\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/android\/","name":"Android"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3502","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/188"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=3502"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3502\/revisions"}],"predecessor-version":[{"id":15812,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3502\/revisions\/15812"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/3503"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=3502"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=3502"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=3502"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}