Devices in short

# Devices in short Devices is the first entry door to the UT use. Presenting tons of adjustable information from many end-points in the community. Forum, discussion, device updates, manuals, statistics. # Introduction Initially developed as an installer site by board member Jan, Devices had a clear goal from its early beginning: to present all UT devices' current progress. Ever since Devices launched, it has been popular among newcomers and Linux users waiting for their smartphones to appear on its list. There was some initial confusion, with intrusive donation requests and pressure to use the installer, which turned it into a slightly weird landing site. However, Jan's simple intention was to create an informative website to complete the missing puzzle. It is worth mentioning that this is still the main portal of arrival for newcomers to the community even today. Thanks to Riccardo who took ownership on the project we solved many issues together by presenting computed scores, indicating issues, pointing to resources, and providing useful information in a very direct way to visitors, helping to ensure a straightforward installation process by solving problems. # The future of Device as a resource I'm highly optimistic that we can unlock its next phase, turning it into a super-resource by setting it towards solving more relevant, up-to-date problems and cementing it as the go-to web service for both porters and users. # Setting new design goals Democratize and capture the community's collective wisdom into a kind of crowdsourced workflow. How can we take the community's collective wisdom and turn it into a crowdsourced workflow? Crowdsourcing is a great way to tap into the collective knowledge of a community, and can be used to create a workflow that is more efficient and effective. There are a number of ways to crowdsource a workflow. One way is to use a social networking platform to create a group or forum that allows community members to share ideas and collaborate on projects. Another way is to use a collaborative writing platform. # SEO Traffic potential When Devices relaunched, the SEO kicked in. As a result, it pulled in more than +3,500 keywords, mostly long-tail results, and positioned the whole domain higher due to its developer-generated content. Since then, new keywords like 'open-source smartphone,' 'Linux phone,' and 'Linux phone,' are already competing alongside Purism, Fairphone, and Pine64 on a fair amount of results - and that is a good progress. Note: > I'm looking for SEO Expert to propose a solid keyword plan Mean while I build an SEO plan of my own to achive better google resualt, I applied meta title, date description, google schema on all pages See track results [here](https://) # Devices value Thanks to Riccardo, Flo, TheKit and many members, who check its accuracy, it has become UBports' primary visual-progress tool, a beautifully designed summary of what UBports has to offer. Its rapid uptake brought demands from the community for some advanced new features, which challenged us to undertake a new round of development, above and beyond the original roadmap. Some may think, "doesn't it overlap the Foundation's Git repository or its "main website?" The clear answer is NO. It is important to recognize what its intended users' want, which is unavailable in that distilled form from any other Foundation resource, focusing as it does on user-centered content. # A few words on the UX process User research is a long and complex process by which designers come to understand how users perceive [product. design. brand]. It takes months and years to build and to justify itself. However, thanks to UT being user-based, we can agile the design process to the audience's needs. Brainstorming sessions led us to believe that improving the UI alone will not solve all our problems. Thus, more accessible user-centered content is needed to simplify porting, answer recurring questions, and balance user decisions, all as part of a coherent solution. # Design Started as one unit of the main site, now taking different direction with system design approach # User journy ## From daily usage to contribute back Our mission as a group of individuals is to build a brand with Ubuntu, the mother distro, to unify the alliance. Therefore, communicating our issue fast is essential in drawing in volunteers who want to be part of the mega-brand. Call to action to contribute all across the documentation and device pages will make it happen, as traffic results show that some copies from A/B testing are working improving the analytics statstics. ### By testing The testing group showes good amount of new entries every week. ### Language Sub Groups Thanks to Wayne for his brilliant idea for creating the Sub community groups; people are discussing and making interaction with the core product. ### Documentation New entries point to a recent new chapter that seems to be getting popular among newcomers, such as the HALium and app section porting section. ### New user The forum sidebar was a smart move still not cashing through google, but analytics show real improvement since the last release of v3 # Recently discovered problems: 1. Users still somewhat having issues navigating community resources (SOLVED) 2. Users still report difficulties understanding how UT perform as OS (SOMEWHAT SOLVED) 3. Porter calls for testers (SOLVED) 4. Inadequate device descriptions (GOT BETTER!!!) 5. Devices not reflecting the US cellular issues (STILL) 6. Some pages are insufficiently objective and imply that a port offers daily driver performance when the the reality is far short of that. 7. Ports are getting abandoned, part-way; flagging them for further work might help to solve that unless they were simply a 'Dead-End' device choice. (SOLVED) 8. Slightly off course: documents need readers' feedback and review. 10. Warning about devices that not survive 20.04 # The general intended audience The user-friendly design enabled the average user to understand and appreciate UBports work, by giving them clear device status updates and detailed instructions. Most of our users are passionate about Linux and are seeking alternatives to the mainstream; they have intermediate Linux backgrounds and can overcome many common issues themselves or by asking for a bit of help. Our mission to give every resource we have at the right place, to enjoy easy access [Persona Profile](https://) wip --- # Roadmap Link to [UI](https://www.figma.com/file/8G0XakAAhFubj0Bm5pE5ei/Final-Website-Ready-For-Bootstrap?node-id=0%3A6273) ### Patch - Device descriptions - Usability/Progress Label - 0 Search resualts - Ubuntu Version ### Minor - Quality Assurance Page - Port Explanation ### Major - RSS - Updated landing page - Automate social posts - Updated device layout (Include forum thread snippest) - Installer page - Porter Page # Scope of work The upcoming improvements and features ## UI Improvement ### Odoo Intergration Seems that Odoo API is blocked ### Forum Inergration Working! ### Quality assurance One page to show all the device MD and point missing details ### Installer Installation steps, report issues and more ### Porting Page Landing page to onboard porters ### Usablity testing page Landing page to encourge testing report - Why should I report? - What does I gain from it? - How do I do that? - Where to start? ### New page: Space for brands. UBports business partners need more. While the "Premium devices" page is locked in the sacred garden of Odoo and doesn't reflect the new market development, I suggest a page where they can push content into a certain design template for "Partners." Offload the content dependency from UBports by proxying it forward, depending on its approval by the foundation. ### Feature request: Direct device bug Report. The detailed sections pointers to the correct repository for bug reports, so people end up in the right place. ### US Signal issue > Rodney: pretty much all of the devices should be able to get 2G signal in the US, and 3G on some carriers, if they aren't USDM devices. Some may or may not be able to get 4G. Carriers that require VoLTE for new device registrations may deny access though. Primary issues are that we don't have VoLTE support in UT, and frequency bands aren't the same for all carriers or regions. --- ## UX Improvement ### Devices description [Started](https://hackmd.io/@kaizen/HykrL2a-F/edit) a document for devices review, open for edit. ### Stash unmatured ports Tuggle bottom will hide premature devices, and non installer device ### Port statues indicator Automated port statue calculated by the score and other indicators ### Implement google schema Improving google accessibility to our Devices would help promote the site and deliver better UX for google results, leading to better SEO. ### RSS feed Explain itself. ### Consumer device price Visitors value transparency; letting them compare apples and/to/with apples would be an excellent addition to each Device and create retention. ## Automation ### Automate score by API request (Under evaluation) Relate features to issues, and when an issue is solved, the score is updated. ### Automate marketing messages New device and progress updates will publish on Twitter and Mastodon. ## Docs: On-site feedback Collect feedback to measure the content's effectiveness in order to improve it. (Ari) # Device stracture * Device page - The main go-to page for UT installation. * Progress section: - Progress bar: weigh the features on a scale of 1-100% - Usability - Making progress vs. not making * Price * Forum 5 last items * [Devices description](https://hackmd.io/@kaizen/HykrL2a-F) * Feature list * Installer * Contributors * External Links * Quality Assurance - The main go-to page for correcting information mainly made of table with all devices, pointing what need to be fix and indicate missing content in the Devices stracture, inviting anyone to fix. # New documents To support the features above. We'll create few documents to support its evolution of devices at docs.ubports.com * New [copy](https://hackmd.io/@kaizen/S1tZdmgQK) for UI * Score explaind * [Kernel and mid-layer explained](https://hackmd.io/@kaizen/HyZqDPwXF) - By Capsia * [How to write the device page](https://hackmd.io/dZ1qzLJqSxqJKV8sTTYQiA) - WIP * [Glossary page](https://hackmd.io/@kaizen/rJKK3iNEY) --- Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0)