{"id":5454,"date":"2026-08-04T19:40:33","date_gmt":"2026-08-04T10:40:33","guid":{"rendered":"https:\/\/smilesoftware.org\/?p=5454"},"modified":"2026-09-23T11:01:30","modified_gmt":"2026-09-23T02:01:30","slug":"android-os%e3%81%ae%e3%82%ab%e3%82%b9%e3%82%bf%e3%83%9e%e3%82%a4%e3%82%ba%e3%81%a7%e3%80%81%e9%80%9a%e4%bf%a1%e4%ba%8b%e6%a5%ad%e8%80%85%e5%90%91%e3%81%91%e3%82%b9%e3%83%9e%e3%83%bc%e3%83%88%e3%83%95","status":"publish","type":"post","link":"https:\/\/smilesoftware.org\/en\/android-os-customization\/","title":{"rendered":"Android OS Customization for Carrier Smartphone Requirements"},"content":{"rendered":"<div class=\"wp-block-group smile-post-content\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><header class=\"smile-article-header\"><div><span class=\"smile-category-pill\">Project<\/span><span class=\"smile-date\"><\/span><\/div><h1 class=\"smile-article-title\">Android OS Customization for Carrier Smartphone Requirements<\/h1><p class=\"smile-excerpt\">Smartphones for the U.S. market require far more than standard Android application development. Devices must support carrier-specific requirements such as SIM lock control, carrier branding customization, standard application adjustments, and user-environment features including RCS and Wi-Fi Calling. To meet these requirements, SMILE provided AOSP and Android Framework customization together with standard application development, delivering devices aligned with carrier deployment specifications.<\/p><\/header>\n\n\n<ul style=\"color:#475569;font-size:17px\" class=\"wp-block-list has-text-color has-link-color wp-elements-cb411721b12d5005927c359075e4811f\">\n<li><strong>Scope:<\/strong> Smartphone Development for U.S. Mobile Carriers<\/li>\n\n\n\n<li><strong>Challenge:<\/strong> SIM lock control, carrier branding customization, standard application customization, and support for U.S.-specific feature requirements<\/li>\n\n\n\n<li><strong>Proposed Solution:<\/strong> Android OS customization, standard application development, device validation, compatibility fixes, and release support<\/li>\n\n\n\n<li><strong>Scope of work:<\/strong> AOSP\/Android Framework, system services, native applications, UI customization, device validation, and compatibility fixes<\/li>\n\n\n\n<li><strong>Timeline:<\/strong> 18 months<\/li>\n\n\n\n<li><strong>Team Structure:<\/strong> Up to 12 team members \/ 180 MM<\/li>\n\n\n\n<li><strong>Implementation Scale:<\/strong> 5 device models, 3 Android versions, and multiple standard applications<\/li>\n<\/ul>\n\n\n<nav class=\"smile-toc\" aria-label=\"Table of Contents\"><h2 class=\"smile-toc__title\">Table of Contents<\/h2><div class=\"smile-toc__grid\"><a class=\"smile-toc__item\" href=\"#section-1\"><b class=\"smile-toc__number\">01<\/b><span class=\"smile-toc__label\">Customer Challenges<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-2\"><b class=\"smile-toc__number\">02<\/b><span class=\"smile-toc__label\">Project Objectives<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-3\"><b class=\"smile-toc__number\">03<\/b><span class=\"smile-toc__label\">SMILE\u2019s Scope of Support<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-4\"><b class=\"smile-toc__number\">04<\/b><span class=\"smile-toc__label\">Key Development and Improvement Points<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-5\"><b class=\"smile-toc__number\">05<\/b><span class=\"smile-toc__label\">Technologies Used<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-6\"><b class=\"smile-toc__number\">06<\/b><span class=\"smile-toc__label\">Technical Challenges and How We Addressed Them<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-7\"><b class=\"smile-toc__number\">07<\/b><span class=\"smile-toc__label\">Implementation Benefits<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-8\"><b class=\"smile-toc__number\">08<\/b><span class=\"smile-toc__label\">Key points for an offshore development structure<\/span><\/a><a class=\"smile-toc__item\" href=\"#section-9\"><b class=\"smile-toc__number\">09<\/b><span class=\"smile-toc__label\">Conclusion<\/span><\/a><\/div><\/nav>\n\n\n<div id=\"section-1\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">01<\/div><h2 class=\"smile-section__title\">Customer Challenges<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Carrier-branded smartphones are subject to much stricter deployment requirements than standard consumer devices. For example, devices must enforce carrier-specific SIM lock policies, allowing only designated carrier SIMs to be used and permitting other SIMs only after predefined conditions are met through an unlock code. In addition, carrier branding requirements extend to the home screen, standard applications, and system settings, making application-level modifications alone insufficient.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">In addition, the devices had to support communication features that are essential in the U.S. market, such as RCS and Wi-Fi Calling. Differences across device models and Android versions often lead to unexpected inconsistencies on actual hardware, even when the same specifications are implemented. As a result, the project required an integrated development approach that covered the Android OS, Android Framework, standard applications, and on-device validation as a unified workflow.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-2\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">02<\/div><h2 class=\"smile-section__title\">Project Objectives<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">The objective of this project was to establish a development platform that enables smartphones to meet carrier deployment requirements and be released reliably. In addition to implementing carrier-specific SIM lock control, branding requirements, standard applications, and communication features, the project focused on building a development foundation capable of maintaining consistency across multiple device models and Android versions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">At the same time, another key objective was to establish an on-device validation process that could identify defects and compatibility issues at an early stage, enabling the team to continuously apply the necessary fixes in each release and improve the overall quality and stability of the product.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-3\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">03<\/div><h2 class=\"smile-section__title\">SMILE\u2019s Scope of Support<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">SMILE was responsible for AOSP\/Android Framework customization, standard application development and enhancement, UI\/UX customization, on-device validation, compatibility fixes, and release support. Beyond application development, SMILE also handled implementation across the boundary between the operating system and applications, as well as device-specific behavior validation to ensure compliance with carrier requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">In addition, SMILE continuously analyzed specifications, clarified requirements, and verified differences across device models and Android versions. Based on these findings, the team identified the key considerations for each release, enabling a consistent development process while minimizing risks arising from variations between devices and operating system versions.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-4\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">04<\/div><h2 class=\"smile-section__title\">Key Development and Improvement Points<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">What was particularly critical in this project was not simply adding functionality at the application layer, but also going deep into AOSP and the Android Framework to ensure that the overall device behavior complied with the telecommunications operator\u2019s stringent requirements. Since SIM lock control and brand customization involve OS-level areas, their implementation requires a deeper understanding than conventional application development.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Furthermore, even when implementing the same specifications, differences across device models and Android versions often resulted in compatibility issues. This required an iterative process of implementation and on-device validation to continuously refine compatibility. SMILE identified and isolated issues across multiple layers\u2014including standard applications, the Android Framework, and hardware interfaces\u2014and progressively improved product stability with each release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Another key aspect of the project was accurately analyzing the large volume of specifications provided by the customer while identifying the priority and impact of each requirement. SMILE established an integrated workflow in which requirement analysis, implementation, and validation were handled by the same team, reducing the risk of overlooked requirements and ensuring that the specifications were consistently reflected in the final product.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-5\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">05<\/div><h2 class=\"smile-section__title\">Technologies Used<\/h2><\/div>\n\n<div class=\"smile-evidence-panels\"><article class=\"smile-evidence-panel\"><div class=\"smile-evidence-panel__mark\"><span class=\"smile-evidence-panel__icon\" aria-hidden=\"true\"><svg class=\"smile-ui-icon smile-ui-icon--replace\" viewbox=\"0 0 64 64\" aria-hidden=\"true\" focusable=\"false\" stroke=\"currentColor\"><path d=\"M14 18h22v16H14z\"\/><path d=\"M28 30h22v16H28z\"\/><path d=\"m42 16 8 8-8 8\"\/><path d=\"M34 24h16\"\/><\/svg><\/span><\/div><div class=\"smile-evidence-panel__body\"><h3 class=\"smile-evidence-panel__title\">Framework \/ OS<\/h3><p>Android AOSP and Android Framework were used to implement operating system\u2013level and system service\u2013level customizations, enabling adjustments to overall device behavior and standard system functionality to meet carrier requirements.<\/p><\/div><\/article><article class=\"smile-evidence-panel\"><div class=\"smile-evidence-panel__mark\"><span class=\"smile-evidence-panel__icon\" aria-hidden=\"true\"><svg class=\"smile-ui-icon smile-ui-icon--flexibility\" viewbox=\"0 0 64 64\" aria-hidden=\"true\" focusable=\"false\" stroke=\"currentColor\"><path d=\"M14 32h26\"\/><path d=\"m32 22 10 10-10 10\"\/><path d=\"M50 18v28\"\/><path d=\"M14 18v28\"\/><\/svg><\/span><\/div><div class=\"smile-evidence-panel__body\"><h3 class=\"smile-evidence-panel__title\">Applications<\/h3><p>Java and Kotlin were used to develop standard applications and device-specific features. The implementation also included carrier-specific UI customization and behavioral enhancements to standard applications.<\/p><\/div><\/article><article class=\"smile-evidence-panel\"><div class=\"smile-evidence-panel__mark\"><span class=\"smile-evidence-panel__icon\" aria-hidden=\"true\"><svg class=\"smile-ui-icon smile-ui-icon--operations\" viewbox=\"0 0 64 64\" aria-hidden=\"true\" focusable=\"false\" stroke=\"currentColor\"><circle cx=\"32\" cy=\"32\" r=\"9\"\/><path d=\"M32 8v8\"\/><path d=\"M32 48v8\"\/><path d=\"m15 15 6 6\"\/><path d=\"m43 43 6 6\"\/><path d=\"M8 32h8\"\/><path d=\"M48 32h8\"\/><path d=\"m15 49 6-6\"\/><path d=\"m43 21 6-6\"\/><\/svg><\/span><\/div><div class=\"smile-evidence-panel__body\"><h3 class=\"smile-evidence-panel__title\">Native \/ Low-Level<\/h3><p>C\/C++ was used to investigate and fine-tune low-level components, including areas close to the Hardware Abstraction Layer (HAL) and hardware interfaces. It was also applied to verify device-specific differences and perform compatibility validation across multiple device configurations.<\/p><\/div><\/article><article class=\"smile-evidence-panel\"><div class=\"smile-evidence-panel__mark\"><span class=\"smile-evidence-panel__icon\" aria-hidden=\"true\"><svg class=\"smile-ui-icon smile-ui-icon--data\" viewbox=\"0 0 64 64\" aria-hidden=\"true\" focusable=\"false\" stroke=\"currentColor\"><path d=\"M12 18c0-5 9-9 20-9s20 4 20 9-9 9-20 9-20-4-20-9z\"\/><path d=\"M12 18v14c0 5 9 9 20 9s20-4 20-9V18\"\/><path d=\"M12 32v14c0 5 9 9 20 9s20-4 20-9V32\"\/><\/svg><\/span><\/div><div class=\"smile-evidence-panel__body\"><h3 class=\"smile-evidence-panel__title\">Data Management<\/h3><p>SQLite and Room were used to manage on-device data and configuration information.<\/p><\/div><\/article><article class=\"smile-evidence-panel\"><div class=\"smile-evidence-panel__mark\"><span class=\"smile-evidence-panel__icon\" aria-hidden=\"true\"><svg class=\"smile-ui-icon smile-ui-icon--quality\" viewbox=\"0 0 64 64\" aria-hidden=\"true\" focusable=\"false\" stroke=\"currentColor\"><path d=\"M16 34 28 46 50 18\"\/><path d=\"M14 14h28\"\/><path d=\"M14 24h18\"\/><path d=\"M14 50h36\"\/><\/svg><\/span><\/div><div class=\"smile-evidence-panel__body\"><h3 class=\"smile-evidence-panel__title\">Testing<\/h3><p>In addition to manual testing on physical devices, carrier-specific test equipment was used to perform device validation, compatibility testing, and performance testing.<\/p><\/div><\/article><\/div><\/div><\/div>\n\n\n\n<div id=\"section-6\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">06<\/div><h2 class=\"smile-section__title\">Technical Challenges and How We Addressed Them<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">The greatest challenge was ensuring that the same carrier requirements could be consistently satisfied across multiple device models and Android versions. Differences in the operating system, Android Framework, device-specific hardware behavior, and dependencies between standard applications meant that a fix working on one model could introduce unintended side effects on another.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Another major challenge was the complexity of the requirements. The customer provided a large volume of specifications covering communication features, SIM lock control, carrier branding, standard applications, and on-device testing conditions. Any misinterpretation or overlooked requirement could directly become a quality risk. To address this, SMILE continuously organized and analyzed the specifications, assessed the impact of each change, validated the implementation on physical devices, and verified differences across releases. Through this iterative process, the team progressively improved compatibility and delivered a stable solution across multiple device models and Android versions.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-7\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">07<\/div><h2 class=\"smile-section__title\">Implementation Benefits<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Through an integrated workflow covering OS customization, standard application enhancement, and on-device validation, SMILE established a process for detecting and resolving issues caused by differences across device models and Android versions before each release. As a result, the development of carrier-compliant devices became more reliable, while ensuring consistent quality across multiple device models.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">In addition, SMILE's capability to work with Android Native at the OS and Framework levels provided the flexibility to address requirements that are difficult to handle through conventional mobile application development alone. This became a key strength in delivering carrier-specific device customization projects.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-8\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">08<\/div><h2 class=\"smile-section__title\">Key points for an offshore development structure<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">Android OS customization projects require more than strong coding skills. They demand the ability to analyze extensive specifications, manage differences across device models, and continuously validate behavior on physical devices. SMILE provides end-to-end support\u2014from requirement analysis and implementation to on-device testing and release support\u2014while applying quality management practices that meet the standards of both Japanese and international projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">In particular, BrSEs and technical leads acted as a bridge between the specifications and the development team, interpreting requirements, organizing device-specific differences, and prioritizing implementation tasks. This enabled SMILE to maintain a stable and efficient development cycle even for highly complex Android OS customization projects.<\/p>\n<\/div><\/div>\n\n\n\n<div id=\"section-9\" class=\"wp-block-group smile-section\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"smile-section__head\"><div class=\"smile-section__number\">09<\/div><h2 class=\"smile-section__title\">Conclusion<\/h2><\/div>\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px\">This case demonstrates SMILE's development support for carrier-grade smartphone projects requiring advanced Android OS customization. By integrating AOSP\/Android Framework customization, standard application development, and on-device validation into a unified workflow, SMILE was able to satisfy device-level requirements while ensuring consistent quality across multiple device models and Android versions. It highlights SMILE's technical expertise in projects that demand deep knowledge of Android Native development and Android OS customization.<\/p>\n<\/div><\/div>\n\n\n<section class=\"smile-article-cta\"><div class=\"smile-article-cta__label\">SMILE Support<\/div><h2>Start a Consultation on GX and DX Initiatives<\/h2><p>From assessing your current situation to implementing systems and improving operations, we work with you to design an approach that fits your company\u2019s needs.<\/p><ul class=\"smile-list\"><li>We can help clarify issues in your current operations and data.<\/li><li>You can design implementation steps that fit your organization\u2019s structure.<\/li><li>You can continue building a framework that remains easy to operate after implementation.<\/li><li>You can use data to verify results and make ongoing improvements.<\/li><\/ul><a class=\"smile-article-cta__button\" href=\"\/en\/contact\/\">Contact us<\/a><\/section><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Devices developed for mobile carriers are subject to stricter requirements than typical smartphone products\u2026&nbsp;<a href=\"https:\/\/smilesoftware.org\/en\/android-os-customization\/\" class=\"\" rel=\"bookmark\">Read More &raquo;<span class=\"screen-reader-text\">Android OS Customization for Carrier Smartphone Requirements<\/span><\/a><\/p>","protected":false},"author":2,"featured_media":5456,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"_themeisle_gutenberg_block_has_review":false,"_ti_tpc_template_sync":false,"_ti_tpc_template_id":"","footnotes":""},"categories":[17],"tags":[33,51,34],"class_list":["post-5454","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project","tag-dx","tag-migration","tag-mobile"],"acf":[],"rttpg_featured_image_url":{"full":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image.png",1672,941,false],"landscape":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image.png",1672,941,false],"portraits":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image.png",1672,941,false],"thumbnail":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-150x150.png",150,150,true],"medium":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-300x169.png",300,169,true],"large":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-1024x576.png",1024,576,true],"1536x1536":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-1536x864.png",1536,864,true],"2048x2048":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image.png",1672,941,false],"trp-custom-language-flag":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-18x10.png",18,10,true],"neve-blog":["https:\/\/smilesoftware.org\/wp-content\/uploads\/2026\/07\/redmine-1611-15358-featured-image-930x620.png",930,620,true]},"rttpg_author":{"display_name":"\u7b20\u539f \u840c","author_link":"https:\/\/smilesoftware.org\/en\/author\/chinh-man\/"},"rttpg_comment":0,"rttpg_category":"<a href=\"https:\/\/smilesoftware.org\/en\/category\/project\/\" rel=\"category tag\">Project<\/a>","rttpg_excerpt":"\u901a\u4fe1\u4e8b\u696d\u8005\u5411\u3051\u7aef\u672b\u3067\u306f\u3001\u4e00\u822c\u7684\u306a\u30b9\u30de\u30fc\u30c8\u30d5\u30a9\u30f3\u88fd\u54c1\u3088\u308a\u3082\u53b3\u5bc6&hellip;&nbsp;Read More &&hellip;","_links":{"self":[{"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/posts\/5454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/comments?post=5454"}],"version-history":[{"count":7,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/posts\/5454\/revisions"}],"predecessor-version":[{"id":6014,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/posts\/5454\/revisions\/6014"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/media\/5456"}],"wp:attachment":[{"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/media?parent=5454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/categories?post=5454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smilesoftware.org\/en\/wp-json\/wp\/v2\/tags?post=5454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}