{"id":3226,"date":"2017-10-31T16:43:15","date_gmt":"2017-10-31T15:43:15","guid":{"rendered":"https:\/\/vizZzion.org\/blog\/?p=3226"},"modified":"2017-11-28T20:31:30","modified_gmt":"2017-11-28T19:31:30","slug":"plasma-mobile-roadmap","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2017\/10\/plasma-mobile-roadmap\/","title":{"rendered":"Plasma Mobile Roadmap"},"content":{"rendered":"<p><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmadoodle-e1509456990471.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmadoodle-e1509456990471-150x300.png\" alt=\"\" width=\"150\" height=\"300\" class=\"alignright size-thumbnail wp-image-3235\" \/><\/a>In the past weeks, we have noticed an increased interest in <a href=\"https:\/\/plasma-mobile.org\/\">Plasma Mobile<\/a> from different sides. Slowly, but surely, hardware vendors have discovered that Plasma Mobile is an entirely different software platform to build products on top of. For people or companies who want to work or invest into Plasma Mobile, it&#8217;s always useful to know where upstream is heading, so let me give an overview of what our plans are, what areas of work we&#8217;re planning to tackle in the coming months and years, where our focus will be and how it will shift. Let&#8217;s talk about <a href=\"https:\/\/community.kde.org\/Plasma\/Mobile\/Roadmap\">Plasma Mobile&#8217;s roadmap<\/a>.<\/p>\n<p>Our development strategy is to build a basic system and platform around our core values first and then extend this. Having a stable base of essentials allows us to focus on an achievable subset first and then extend functionality for more and more possible target groups. It avoids pie-in-the-sky system engineering something that will never be useful and designed for a unicorn market that never existed. Get the basics right first, then take it to the next levels. These levels are:<\/p>\n<ol>\n<li>Prototype (already finished)<\/li>\n<li>Feature Phone<\/li>\n<li>Basic Smartphone<\/li>\n<li>Featured Smartphone<\/li>\n<\/ol>\n<p><figure id=\"attachment_3241\" aria-describedby=\"caption-attachment-3241\" style=\"width: 885px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr.png\" alt=\"Plasma Mobile Roadmap\" width=\"885\" height=\"253\" class=\"size-full wp-image-3241\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr.png 885w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr-400x114.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr-768x220.png 768w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2017\/10\/plasmaprogr-300x86.png 300w\" sizes=\"auto, (max-width: 885px) 100vw, 885px\" \/><\/a><figcaption id=\"caption-attachment-3241\" class=\"wp-caption-text\">Plasma Mobile Roadmap<\/figcaption><\/figure><br \/>\nLet&#8217;s look at these steps in detail.<\/p>\n<h2>Prototype and Product Vision<\/h2>\n<p>The <a href=\"https:\/\/dot.kde.org\/2015\/07\/25\/plasma-mobile-free-mobile-platform\">first public release<\/a> of Plasma Mobile was this prototype. It showed a very basic and incomplete-for-daily-use system on actual, modern smartphone hardware. You could make phone calls, start and manage apps, and manipulate some basic system functionality. It showed a smartphone system based on Plasma could be done, and more importantly, it taught us a lot about where we want to take things on a technical level.<br \/>\nAlong with the prototype, we developed a product vision for Plasma Mobile, a direction where we want to take it (emphasis added by yours truly):<\/p>\n<blockquote><p>\n&#8220;Plasma Mobile aims to become a complete software system for mobile devices. It is designed to give <strong>privacy-aware<\/strong> users back the full-control over their information and communication. Plasma Mobile takes a <strong>pragmatic<\/strong> approach and is <strong>inclusive<\/strong> to 3rd party software, allowing the user to choose which applications and services to use. It provides a <strong>seamless experience across multiple devices<\/strong>. Plasma Mobile implements <strong>open standards<\/strong> and it is developed in a transparent process that is <strong>open for the community to participate<\/strong> in.&#8221;\n<\/p><\/blockquote>\n<h2>Feature Phone<\/h2>\n<p>The feature phone milestone is what we&#8217;re working on right now. This involves taking the prototype and fixing all the basic things to turn it into something usable. Usable doesn&#8217;t mean &#8220;usable for everyone&#8221;, but it should at least be workable for a subset of people that only rely on basic features &#8212; &#8220;simple&#8221; things.<br \/>\nCore features should work flawlessly once this milestone is achieved. With core features, we&#8217;re thinking along the lines of making phone calls, using the address book, manage hardware functions such as network connectivity, volume, screen, time, language, etc.. Aside from these very core things for a phone, we want to provide decent integration with a webbrowser (or provide our own), app store integration likely using <a href=\"https:\/\/store.kde.org\">store.kde.org<\/a>, so you can get apps on and off the device, taking photos, recording videos and watching these media. Finally, we want to settle for an SDK which allows third party developers to build apps to run on Plasma Mobile devices.<br \/>\nGetting this to work is no small feat, but it allows us to receive real-world feedback and provide a stable base for third-party products. It makes Plasma Mobile a viable target for future product development.<\/p>\n<h2>Basic Smartphone<\/h2>\n<p>The basic smartphone extends the feature set of Plasma Mobile to a wider group of target users. The plan is to add personal information management features, such as reading and sending emails, calendaring and reminders. We also want to add file management capabilities in this milestone, because we think that the user should be able to deal with the data in her phone in the most transparant way, and file management is something that allows users to look into the fabric of their data, and that of the phone itself. Another big topic for the Basic Smartphone milestone is extending the app ecosystem through third-party and original applications to allow the user to do more things with the device.<\/p>\n<h2>Featured Smartphone<\/h2>\n<p>For the featured smartphone, we want to add more system-level integration features such as deeply integrated private cloud storage and have grown our own ecosystem with more apps and of course games. An often requested feature is support for Android apps. Supporting Android apps could give Plasma Mobile a huge boost in terms of possible target groups, since it allows users to switch away from Android more easily, even when they are requiring a few apps and can&#8217;t really live without these. Being able to run Android apps on a Plasma Mobile device can ease the transition considerably and it allows us to capture potential target user groups that rely on proprietary services which Plasma Mobile, at first, cannot serve simply because as a smaller player, it&#8217;s not an attractive enough platform to have the likes of WhatsApp develop native clients for.<\/p>\n<h2>When it&#8217;s ready!?<\/h2>\n<p>On purpose, we did not add a specific timeline to this roadmap for two reasons: First, Plasma Mobile is a participative project, if you want to see something done, get involved. We&#8217;re not running the show all by ourselves. We want to create an open eco system where people who do the work decide on its direction. This means if you get involved, you can help us shape the future of mobile computing instead of being just a code monkey that does what someone else has decided. Secondly, we don&#8217;t want to deliver half-assed software just because we set a timeline. We want to create quality software to build products upon. If you or your company want to ship on a specific date, work with us and we&#8217;ll plan together. We won&#8217;t make promises when something is ready beforehand, but as an upstream project, we want to ship &#8220;when it&#8217;s ready&#8221;. This &#8220;when&#8221; depends on all our input and hard work. So don&#8217;t sit in your armchairs and wait for someone else to do the heavy lifting, but let&#8217;s get cracking!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the past weeks, we have noticed an increased interest in Plasma Mobile from different sides. Slowly, but surely, hardware vendors have discovered that Plasma Mobile is an entirely different software platform to build products on top of. For people or companies who want to work or invest into Plasma Mobile, it&#8217;s always useful to&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2017\/10\/plasma-mobile-roadmap\/\">Continue reading <span class=\"screen-reader-text\">Plasma Mobile Roadmap<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,22,29,25,28,32,43],"tags":[],"class_list":["post-3226","post","type-post","status-publish","format-standard","hentry","category-android","category-english","category-kde","category-linux","category-mobile","category-plasma","category-privacy"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3226","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=3226"}],"version-history":[{"count":15,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3226\/revisions"}],"predecessor-version":[{"id":3244,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3226\/revisions\/3244"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=3226"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=3226"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=3226"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}