<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts of Victoria Chen RSS</title><link><![CDATA[https://ci.una.io/test3/m/posts/rss/author/28]]></link><atom:link href="https://ci.una.io/test3/m/posts/rss/author/28" rel="self" type="application/rss+xml" /><description>Posts of Victoria Chen RSS</description><lastBuildDate>Thu, 01 Feb 2024 09:00:32 GMT</lastBuildDate><item><title><![CDATA[Sometimes we fly too close to the dashboard]]></title><link><![CDATA[https://ci.una.io/test3/view-post/sometimes-we-fly-too-close-to-the-dashboard]]></link><guid><![CDATA[https://ci.una.io/test3/view-post/sometimes-we-fly-too-close-to-the-dashboard]]></guid><description><![CDATA[<p>Last Sunday I sat on the porch with a coffee and, for once, no laptop. Mild for the end of January, birds busy in the hedge, a neighbour's wind chime doing its thing. I closed my eyes for what I thought was a minute. It was closer to twenty.I spend most of my working week inside dashboards: activation rates, day-7 retention, how many new members post in their first week. I like numbers and I'll defend them in any meeting. But that morning I noticed how rarely I give my attention to anything that isn't being measured.The thing the chart can't seeA client asked me recently why their retention dipped in January. We pulled every cohort chart we had. The real answer came from a moderator who mentioned, almost in passing, that the member who used to welcome every newcomer had gone quiet over the holidays. No metric tracked her. She was the onboarding flow.That's what I mean by flying too close. Stare at the numbers long enough and you start managing the chart instead of the community.What I'm trying insteadOne morning a week with no dashboards at all. I read member posts in full instead.Every metrics review opens with a single member story before any chart goes up.When a number moves, the first question is "who?" before "why?"The numbers will still be there on Monday. The person quietly holding your community together might not be, if nobody notices them.</p><img src="https://ci.una.io/test3/s/bx_posts_photos_resized/dygr6x9sxxgb85wpmuupef3wzrmucjka.jpg" />]]></description><pubDate>Thu, 01 Feb 2024 09:00:32 GMT</pubDate></item><item><title><![CDATA[Supercharging Networking Apps: Where the Stack Pays for Itself]]></title><link><![CDATA[https://ci.una.io/test3/view-post/supercharging-networking-apps-where-the]]></link><guid><![CDATA[https://ci.una.io/test3/view-post/supercharging-networking-apps-where-the]]></guid><description><![CDATA[<p>Clients ask me two questions about a new community platform: what will it cost to build, and what will it cost to keep running? The second matters more. Over a three-year life, maintenance and support usually outweigh the initial build, so that is the lens I use here. Where does each part of this stack save time or money?Piece by piecePHP and MySQL: inexpensive, widely available hosting, a deep hiring pool and a mature ecosystem. A backend you can staff and host without surprises, and the database where retention and churn analysis starts.React: a fast, responsive interface shows up in engagement numbers, and reusable components mean a bug gets fixed once instead of in five places.React Native: one codebase for iOS and Android. In the projects I have reviewed, shared code cut mobile build effort by a third to a half.REST API: one contract serves the web app and both mobile apps, so changes are made and tested once.Next.js: server-side rendering and static pages make public content fast and easy for search engines to find, which lowers the cost of acquiring members.Tailwind CSS: shared styles across web and mobile mean fewer "make it match" design rounds.None of these savings is dramatic on its own. Together they compound, especially for small teams where the same two people build, support and grow the product.My three-question checklistWhat does it cost to run in year three, not year one?How easily can you hire for it?Can you measure what members actually do?This stack scores well on all three. That doesn't make it right for every project, but it is a solid default for a community that plans to grow.</p><img src="https://ci.una.io/test3/s/bx_posts_photos_resized/brq5ynn6jb6m8b43xs3qbjshtwngxhum.jpg" />]]></description><pubDate>Thu, 13 Jul 2023 08:29:44 GMT</pubDate></item><item><title><![CDATA[Cost Efficiency and Maintenance Benefits of Using an Open-Source Platform with PHP Backend, UNA Framework, React, and React Native]]></title><link><![CDATA[https://ci.una.io/test3/view-post/cost-efficiency-and-maintenance-benefits]]></link><guid><![CDATA[https://ci.una.io/test3/view-post/cost-efficiency-and-maintenance-benefits]]></guid><description><![CDATA[<p>When building a networking site, cost efficiency and ease of maintenance are crucial considerations. Utilizing an open-source platform with a PHP backend, such as the UNA Framework, along with React for the frontend and React Native for mobile apps, provides numerous benefits that make it the ideal choice for minimizing support overhead and long-term maintenance costs.1. Cost Savings with Open-Source TechnologiesBy leveraging open-source technologies like the UNA Framework, React, and React Native, you eliminate the need for costly licensing fees. Open-source solutions are freely available and supported by vibrant communities, ensuring ongoing updates, bug fixes, and feature enhancements without any additional financial burden.2. Flexibility and CustomizationOpen-source platforms provide unparalleled flexibility and customization options. With UNA Framework, you have full control over your backend development, allowing you to tailor the networking site to meet specific requirements. React and React Native, being highly modular and extensible, offer limitless possibilities for frontend development and mobile app creation.3. Wide Community SupportOpen-source platforms benefit from large and active communities. This means you can tap into a wealth of resources, documentation, forums, and tutorials, making it easier to find solutions to any challenges you may encounter. The community support significantly reduces the support overhead and enables faster issue resolution.4. Shared Codebase and Simplified MaintenanceDeveloping both the frontend and mobile apps with React and React Native allows for a shared codebase, reducing duplication of efforts and simplifying maintenance. Any updates or bug fixes applied to the shared codebase automatically reflect across web and native platforms, saving time and effort in maintaining separate codebases.5. Long-Term Scalability and MaintainabilityUsing a PHP backend, UNA Framework, React, and React Native provides a robust foundation ... <a href="https://ci.una.io/test3/view-post/cost-efficiency-and-maintenance-benefits">Read more</a></p><img src="https://ci.una.io/test3/s/bx_posts_photos_resized/ytrrndpcuibe4ywrwzfwqkczmsww7glu.jpg" />]]></description><pubDate>Wed, 28 Jun 2023 06:22:49 GMT</pubDate></item></channel></rss>