<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ritesh Kanchi on Medium]]></title>
        <description><![CDATA[Stories by Ritesh Kanchi on Medium]]></description>
        <link>https://medium.com/@riteshkanchi?source=rss-5a56cf738ae6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8Mph8tDD8WwfZXYtHgYS8A.jpeg</url>
            <title>Stories by Ritesh Kanchi on Medium</title>
            <link>https://medium.com/@riteshkanchi?source=rss-5a56cf738ae6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:19:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@riteshkanchi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When Scaling Isn’t Enough: Toward Durable Accessibility]]></title>
            <link>https://riteshkanchi.medium.com/when-scaling-isnt-enough-toward-durable-accessibility-756eb01c0435?source=rss-5a56cf738ae6------2</link>
            <guid isPermaLink="false">https://medium.com/p/756eb01c0435</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Ritesh Kanchi]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 05:55:20 GMT</pubDate>
            <atom:updated>2026-02-20T06:09:38.404Z</atom:updated>
            <content:encoded><![CDATA[<h4>A reflection on my time researching/teaching/doing accessibility for large computing courses</h4><figure><img alt="A greyscale photo of a large, durable tree growing out of the ground surrounded by plants and fauna." src="https://cdn-images-1.medium.com/max/1024/1*VTqMOa7oqVcGsgZ8uCI78A.jpeg" /></figure><p>This idea jokingly came up as a “post-mortem” for <a href="https://g.riteshkanchi.com/sigcse26-systems-for-scaling-accessibility/">“Systems for Scaling Accessibility in Large Computing Courses”</a> — a SIGCSE experience report I co-wrote with the amazing <a href="https://homes.cs.washington.edu/~mnats/">Miya Natsuhara</a> and <a href="https://matthewwang.me/">Matt Wang</a>. In the experience report, we discuss how we developed four systems to scale accessibility efforts in a large introductory programming course sequence, with over 3500 enrolled students and 100 teaching assistants (TAs) per year.</p><p>If you want to learn more about those systems and what we did, you can read the paper. This post is more about the aftermath, and how these systems fared.</p><p>But it’s also about my reflection on our accessibility efforts as a teaching assistant/research scientist at the University of Washington (UW) — and how I feel a year later, with this work persisting (in one way or another.)</p><p><em>This post is extremely inspired by a talk I gave at the AccessComputing SIGCSE TS 2026 Affiliated Event. In fact, at least 80% of it is from that presentation!</em></p><p>In this post, I hope to reflect on a few things:</p><ul><li>Accessibility as an ecosystem of <strong>labor</strong> in large computing courses</li><li>The fragility that emerges when scaling systems for accessibility efforts</li><li><strong>Reflections</strong> and <strong>tensions</strong> as a student practitioner</li><li>Durable accessibility as a <strong>vision</strong> for accessible computing education infrastructure</li></ul><p>I find that caring about accessibility, especially in education, requires both honesty and humility in knowing what breaks; but moreso, learning to know what one can do to “unbreak” it.</p><h3>Ecosystems of labor</h3><p>CSE 12X is the UW’s introductory programming sequence, made up of three courses: CSE 121 (for students with no programming experience), CSE 122 (for students with some programming experience), and CSE 123 (for students with substantial programming experience.) For those on the semester system, think of CSE 121 + 122 = CS1, and CSE 122 + 123 = CS2.</p><p>As mentioned, we have 3500+ enrolled UW students taking these courses yearly, and employ 100+ undergrad TAs to help manage the large course sizes. We can represent the students, TAs, as well as the instructor, as existing within an ecosystem of labor:</p><figure><img alt="A diagram of instructors, TAs, and students. Instructors are a single blue node, TAs are a 2x2 grid of green nodes, and students are a large cluster of orange nodes." src="https://cdn-images-1.medium.com/max/1024/1*jLF2fDbDFMailAhJ3psaqQ.png" /><figcaption>Large computing courses are ecosystems of labor</figcaption></figure><p>Each of these actors: Instructors, TAs, and Students, all perform some amount of labor in a course. Instructors exert labor in leading the course, giving lectures, and course minutiae. TAs exert labor in teaching recitation section, hosting office hours, and grading (much to their dismay.) And students exert labor in attending lecture and recitation section, doing assignments and projects, and just being students of the course!</p><p>So while this is the ecosystem of labor in a large computing course, when we think about accessibility, it’s naive to think they remain the only actors.</p><p>Accessibility in large computing courses reveals a larger ecosystem of labor:</p><figure><img alt="A diagram of instructors, TAs, students, institutional staff, experts, and student supports. Instructors are a single blue node, TAs are a 2x2 grid of green nodes, and students are a large cluster of orange nodes. Instiutional staff are three yellow nodes, experts are a single pink node, and student supports are three purple nodes." src="https://cdn-images-1.medium.com/max/1024/1*FbiUa7TN-UMNlA_KsUQN-g.png" /><figcaption>Accessibility as an ecosystem of labor</figcaption></figure><p>Among the original actors, their labors have expanded; it takes both time and labor for students to advocate for their disabilities. It takes further labor from the course staff to learn about accessibility, create accessible materials, and teach accessibly.</p><p>But we also expand the actors in the labor ecosystem: Institutional Staff, comprised of administration and institution-level offices; Experts, both on- and off-campus who can provide expertise and guidance; and Student Supports, which I define as student-facing groups focused on support and advocacy, such as Disability Services Offices (which also fall under Institutional Staff, in a non-student-facing capacity) and Assistive Technology Centers.</p><h4>Interactions of accessibility labor</h4><p>It’s worth discussing the interactions of this ecosystem, as actors of ecosystems are often in multiple, chained interactions across other actors.</p><p>Some of these interactions include:</p><ul><li><strong>Accommodation Coordination</strong> (Instructors ↔ Student Supports ↔ Students)</li><li><strong>Infrastructure &amp; Policy Guidance</strong> (Institutional Staff ↔ Experts ↔ Student Supports ↔ Instructors)</li><li><strong>Knowledge Transfer &amp; Training </strong>(Experts ↔ TAs ↔ Instructors)</li><li><strong>Curricular Integration &amp; Iteration</strong> (Instructors<strong> </strong>↔ TAs ↔ Students)</li><li><strong>Everyday Accessibility Practices</strong> (TAs ↔ Students)</li></ul><p><strong>Accessibility lives in these interactions.</strong> But scaling cannot rely on these interactions alone.</p><h3>The dimensions of infrastructure</h3><p>Scaling systems is not the same as building infrastructure. Susan Leigh Star, a renowned American sociologist, wrote on <a href="https://ics.uci.edu/~wscacchi/GameLab/Recommended%20Readings/ethnography-infrastructure-Star-1999.pdf"><em>The Ethnography of Infrastructure</em></a>, where she and her colleagues defined dimensions of infrastructure.</p><p>Of these dimensions, I find that our systems for scaling accessibility don’t actually classify as a proper infrastructure:</p><ul><li>❌ <strong>Embeddedness</strong> — the labor of accessibility is built upon interactions and systems, each meshing into the other; our systems don’t consider this deeply</li><li>❌ <strong>Transparency</strong> — our systems were often being reinvented and reintroduced</li><li>✅ <strong>Reach or Scope</strong> — our systems had both wide and narrow reaches/scopes</li><li>❌ <strong>Learned as a part of membership </strong>— students encounter accessibility inconsistently, and course staff don’t learn it easily in our systems</li><li>❌ <strong>Links with conventions of practice</strong>—since we lack a focused community of practice, our systems are unable to both shape and be shaped by the community’s conventions</li><li>❌ <strong>Embodiment of standards</strong> — our systems lack transparency by not connecting into other infrastructures in a standardized way</li><li>✅ <strong>Built on an installed base </strong>— our systems wrestle with the inertia of the existing courses and inherits strengths and limitations from the courses</li><li>✅ <strong>Is fixed in modular increments, not all at once or globally</strong> — our systems are designed to be adopted through smaller changes and interventions</li><li>✅ <strong>Becomes visible upon breakdown </strong>— our systems, when broken, are extremely visible</li></ul><p>It’s especially easy to develop more systems, or expand our systems to symptomatically address these unmet dimensions; but what we lacked wasn’t more tools or processes. <strong>Without a proper consideration of infrastructure, scaled systems become fragile.</strong></p><h3>System fragility</h3><p>In the time since leaving UW, I’ve been in the unique position to still be apart of their accessibility efforts (albeit, on the opposite coast.) And it’s with this position that I’ve been able to isolate several dimensions of system fragility. In the following fragilities, I’ll use CSE 12X as a case study.</p><h4>Turnover over time</h4><p>One of the major fragilities is the turnover of faculty, TAs, and students. For CSE 12X, it’s often the case that a different faculty member will teach each quarter. If we’re lucky, the same faculty member will stay for two, or even three quarters in a row. This is also exacerbated by the fact that there are summer instructors, who are often not faculty members and teach significantly smaller courses.</p><p>Furthermore, the TA and student bodies are everchanging. Students and TAs come, go, and graduate. What’s important to notice here, however, is that a subset of students eventually become TAs. So their experience of being a student in CSE 12X is vital to their perspective and actions as a TA.</p><figure><img alt="A diagram that shows term-by-term rotations for Fall 2025, Winter 2026, and Spring 2026. Each term: there is a new faculty member; there are new TAs and some TAs leave; and there are new students with some going on to become TAs." src="https://cdn-images-1.medium.com/max/1024/1*SaoAvhBiJlkJU1rjd2rr7Q.png" /></figure><p>From an accessibility perspective, what does this mean? Well, there are several implications of this turnover:</p><ul><li>Accessibility often needs to be reintroduced as new TAs are onboarded</li><li>Faculty priorities may change from quarter-to-quarter</li><li>Practices resurface, and then fade</li><li>Efforts are restarted, or deprioritized</li></ul><p>In a nutshell, accessibility is deeply coupled to individual efforts — and lack persistence.</p><h4>Finite capacity and bandwidth</h4><p>As we’ve seen with the earlier labor ecosystems, these groups are already stretched thin, which makes it difficult to always make meaningful progress on accessibility.</p><p>It’s important to acknowledge these capacities:</p><ul><li><strong>TAs</strong> — Students who also teach, grade, and support the course</li><li><strong>Instructors</strong> — Lead course direction while balancing teaching, <br>research, service, and other responsibilities</li><li><strong>Institutional Staff, Student Supports, and Experts</strong> — Provide shared infrastructure and periodic support institution-wide</li></ul><p>It can feel hard to consistently practice accessibility, especially as courses ebb and flow throughout a term. A similar tension is that accessibility can’t be the only priority of a course either: new assignments, quizzes, and exams are constantly needed, among other variations every quarter.</p><p>We also noticed similar capacity constraints in the trainings we conducted; often time-bound, forcing us to prioritize practices, which directly influenced the types of accessibility efforts TAs conducted.</p><h4>Fragmented and localized knowledge systems</h4><p>Finally, I’ve noticed frictions in how individuals learn and practice accessibility.</p><ul><li><strong>Tacit &amp; Informal Knowledge</strong> — as a research scientist, a lot of my own knowledge around accessible CS was built up through practice and experiences I personally had; informal conversations, visits to groups/people across campus, and experimentation. Policies and guides are great, but only detail rules, not necessarily actions — which are harder to strictly define.</li><li><strong>Fragmented Information</strong> — Notion, Google Docs, Slack, Discord, White Boards, and Sticky Notes; information is deeply fragmented across platforms and modalities. Furthermore, individuals don’t know how to sort through it when they are trying to learn or practice accessibility.</li><li><strong>Locally Developed — </strong>accessibility improvements emerge where dedicated effort exists, and often stay where they emerged. Even though CSE 12X is a sequence, courses operate in some level of autonomy. For example, I developed accessible resource pipelines in Spring 2024 for CSE 121. Eight quarters later, CSE 122 and 123 do not have the system integrated, even though it would be relatively easy to do so.</li><li><strong>Context Dependence</strong> — similar to the prior friction, efforts don’t always translate, as not all courses share the same accessibility challenges. For example, teaching HelloWorld.java accessibly is <a href="https://g.riteshkanchi.com/chi26-arboretum/">a very different challenge than making a binary tree with a height of 10 accessible</a>.</li></ul><p>These are a subset of the total fragilities, but what I identify to be the most significant fragilities facing our systems.</p><h3>A vision of Durable Accessibility</h3><p>We often discuss the sustainability of systems, but what good is sustainability if it is of variable and fragile effort, practice, and execution? <strong>Durability is the infrastructural capacity that allows scaled systems to persist.</strong></p><h4>Surviving turnover through integration</h4><p>We can’t stop turnover; it’s a natural fragility. Accessibility must persist beyond individuals and be embedded in the course itself. It’s only with this consideration that accessibility does not need to be reintroduced from scratch each term, but can be a deep consideration into the course itself — all the way to the students.</p><figure><img alt="A diagram showing that course accessibility practices should be embedded into the course, irregardless of term, faculty, TAs, or student turnover." src="https://cdn-images-1.medium.com/max/1024/1*-6LMXXV8W2z3UX5E8XCjSw.png" /></figure><p>Obviously, we will need to still introduce accessibility; but it can come in the curricula, but also part of continuations of the previous quarter’s efforts. There’s flexibility in how it’s presented and introduced, as long as the practices themselves are embedded into the course itself.</p><h4>Designing for accessibility within finite capacities</h4><p>Durable accessibility must operate <em>within</em> existing instructional roles and workflows — not as additional labor. It’s when accessibility is seen as additional labor that it becomes easily neglected, awaiting symptomatic improvements. Some suggestions I propose include:</p><ul><li><strong>Embed accessibility into TA onboarding</strong></li><li><strong>Make accessible practice the default expectation</strong></li><li><strong>Integrate accessibility into required workflows</strong></li></ul><p>These are difficult to do, but over time, will become, simply, part of the process of running large computing courses. Establishing more consistent training efforts is another consideration — accessible teaching often equals good teaching. This removes the forced time constraint upon trainings, and decrease the previous prioritization of practices shown.</p><h4>Developing legible and transferable practice</h4><p>To describe how we can make knowledge systems durable, I will use an iceberg. Above the water are knowledge systems such as: Templates, Documentation, Policies, and Trainings. All great!</p><p>Templates are misapplied. Documentation goes unread. Policies are misunderstood. Trainings don’t stick.</p><figure><img alt="A picture of an iceberg with examples of knowledge both above and below the water." src="https://cdn-images-1.medium.com/max/1024/1*EiK5WMaO9nSS4kdMMar1CA.png" /><figcaption>An iceberg of knowledge</figcaption></figure><p>Under the water exists the real knowledge we should be sharing. What it means to design accessible slides with the templates. <a href="http://bookish.press/tac">How we might develop curriculum that integrates accessibility</a>. Why testing content with a screen reader matters. Knowledge systems must be made legible and transferable, in ways that are both meaningful and ways that stick. It’s when content doesn’t stick or is difficult to uncover where mistakes, misinterpretations, and a lack of action occur.</p><p><strong>Accessibility in large computing courses is not only about scaling efforts — it is about building durable infrastructure that allows those efforts to persist.</strong></p><p>So what now?</p><p>In the short term, I hope to revisit our systems with Durable Accessibility in mind — not to build more tools and processes, but to build stronger infrastructure and develop intentional scaffolding. Durability means ensuring that accessibility efforts can survive turnover, capacity constraints, and fragmented knowledge. Without it, even well-designed systems become fragile.</p><p>With ADA Title II compliance on the horizon — and accessibility increasingly central to how we teach — we cannot afford to treat accessibility symptomatically. We need infrastructures that allow accessibility practice to persist beyond individuals, beyond terms, and beyond moments of urgency.</p><p>I’ve often felt that accessible education practices must be both visible (available and usable) and transparent (honest about what works and what breaks.) Now more than ever, we need to share not only resources, but processes and infrastructures that enable accessibility work to last.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=756eb01c0435" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Applying to HCI PhDs]]></title>
            <link>https://riteshkanchi.medium.com/applying-to-hci-phds-7422f490fef1?source=rss-5a56cf738ae6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7422f490fef1</guid>
            <category><![CDATA[phd-application]]></category>
            <category><![CDATA[hci]]></category>
            <dc:creator><![CDATA[Ritesh Kanchi]]></dc:creator>
            <pubDate>Sat, 03 Jan 2026 06:42:15 GMT</pubDate>
            <atom:updated>2026-09-25T14:13:25.769Z</atom:updated>
            <content:encoded><![CDATA[<h4>A (hopefully) helpful guide on applying to HCI PhD programs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5s4iBgCIXNbvrls-810XPA.png" /></figure><p>Applying for your PhD is hard.</p><p>That’s it. That’s the post.</p><p>While I found applying to my PhD being a time-consuming, stressful, and a self-doubting process, I also found it extremely beneficial in answering one question: “What do I want to do?” If there’s anything that will make you question whether you want to do a PhD, it’s this; and not because you aren’t passionate about doing one: because you have a hard time conveying why.</p><p>With this in mind, I’ve divided this post into four sections:</p><ul><li><a href="https://g.riteshkanchi.com/blog/applying-to-hci-phds/#before-you-apply">Before you apply</a>: How to find the right programs and potential advisors</li><li><a href="https://g.riteshkanchi.com/blog/applying-to-hci-phds/#applying">Applying</a>: Writing your statement of purpose and personal statement</li><li><a href="https://g.riteshkanchi.com/blog/applying-to-hci-phds/#interviewing">Interviewing</a>: What to expect, how to prepare, and how to recover from it</li><li><a href="https://g.riteshkanchi.com/blog/applying-to-hci-phds/#deciding">Deciding</a>: How to decide on the right program, advisor, funding, and research focus</li></ul><p>Kinda a “What do I wish I had known before I had applied?” of sorts.</p><p>The thing is, applying to your PhD isn’t like applying your undergrad, or maybe even your masters. It’s a whole other beast, and it can be a very different experience for everyone. There is going to be a lot of self-reflection, research, and planning. And it’s not just about getting into a program: you want to find the right fit for you, your research interests, and (dare I say) your career goals. Since you’ve applied to undergrad/masters, you may have a better idea of what you want to do, but that doesn’t mean you need everything figured out. In fact, I think one of the biggest mistakes you can make is to think that you need to have everything figured out before applying.</p><p>While this post is focused on human-computer interaction (HCI) PhDs, I think the advice here can be applied to other PhD programs as well. But I will preface this by saying that I can’t speak to the specifics of those programs, and how the application process differs; but the core principles of self-reflection, research focus, and fit remain the same.</p><p>I hope that this post can be a helpful resource for you, and that it can help you navigate the application process with a bit more confidence and clarity.</p><h3>Before you apply</h3><p>The first step in applying to a PhD program is to figure out, “Do I really want to do a PhD?”</p><p>I recommend reading the following posts to help you answer this question:</p><ul><li><a href="http://100rsns.blogspot.com/p/complete-list-to-date.html">100 (really 98) reasons NOT to go to grad school</a></li><li><a href="https://motivatedacademic.com/why-to-do-a-phd/">7 good reasons to do it</a></li></ul><p>One of my professors sent me these (out of support), and I think they are a great starting point for thinking about whether or not you want to do a PhD. <em>Notice how 100 &gt; 7?</em></p><p>If you know you want to do a PhD, the second step is to do your research; which makes sense, given that you’re applying to do research. But there’s nuance to this, and it can be a bit overwhelming. I think there are three main areas to focus on:</p><ul><li>Finding your focus: What do you want to research? What are your interests? What are your strengths?</li><li>Programs: What programs are out there? What are their strengths? What are their weaknesses?</li><li>Advisors: Who are the potential advisors? What are their research interests? Do they align with yours?</li></ul><h3>Finding your focus</h3><p>I think my own PhD advisor, Krzysztof Gajos, <a href="https://kgajos.seas.harvard.edu/join-our-group/for-prospective-phd-students/#:~:text=In%20your%20Statement,like%20to%20create.">put it best</a>:</p><blockquote><em>…you also need to communicate what you are interested in. This is a little tricky. On the one hand, it really helps if you can include some specific examples of problems that fascinate you. On the other hand, you do not want to create an impression that the example problems are the only ones you are interested in. An effective strategy I’ve seen some applicants use is to say something like “I am broadly interested in problems [that have the following characteristics]. For example, …”. Also, remember that PhD research is about creating generalizable knowledge that does not yet exist (while most of undergraduate courses are about applying existing knowledge to solve specific problems). While you are not expected to translate your ideas into the technical vocabulary of your intended field, try to identify general challenges rather than specific products or solutions you’d like to create.</em></blockquote><p>Maybe you’ve done some research in undergrad, or maybe you’ve worked on a project that you’re really passionate about. Or maybe you want to go in a completely different direction. Whatever it is, you need to have a clear idea of what you want to research, and why. This will help you narrow down your search for programs and advisors, and it will also help you write your personal statement and research statement.</p><p>Some questions I found helpful to ask myself were:</p><ul><li>What do I want to learn more about?</li><li>What problems do I want to solve?</li><li>What do I want to create?</li><li><em>insert more questions to ask yourself here</em></li></ul><p>It’s also okay if you can’t specifically describe your research focus. I think it’s more important to have a general idea of what you’re interested in, and to be able to articulate that in a way that shows you’re passionate about it. You can always refine your focus later on, but having a starting point is crucial.</p><h3>Programs &amp; Advisors</h3><p>It’s really easy to go to <a href="https://csrankings.org/">CSRankings</a> and look at the top HCI programs. In fact, if you’re content with just looking at rankings, you can stop reading this post now!</p><p>There’s an easily-noticed correlation between the number of HCI faculty and the number of accepted HCI papers, which is why the top HCI programs are often the ones with the most faculty. But that doesn’t mean they’re the right fit for you. Rather than programs, I think it’s more important to focus on finding the right advisors to apply to.</p><p>When I made my original list of programs to apply to, I made the mistake of choosing schools I had a connection to (UW, UMich, and CMU); but one of my undergrad advisors, very quickly pointed out that I should be looking at the faculty, not the programs. I would recommend:</p><ul><li>Looking at the conferences you would like to publish in, and seeing which faculty are publishing there</li><li>Looking at the faculty’s research interests and recent publications, and seeing if they align with yours</li><li>Looking at their current students, seeing their research interests and recent publications</li><li>Thinking about what you can bring to the table and what you can learn from them</li></ul><p>Most programs will ask you to apply to three faculty members; but remember, the majority of HCI groups are small, and might only have one or two faculty members. So, if you’re applying to a program with only one HCI faculty member, you should be sure that their research aligns with your interests. Don’t just apply to the program because it’s a top-ranked school; apply to it because you want to work with that faculty member. Many schools will ask you to write a brief description of why you’d like to work your selected advisors as well.</p><p>This person will be your advisor and part of your support system for the next 5 years, so determining if they are a good fit (research-wise) for you is crucial. In the <a href="https://g.riteshkanchi.com/blog/applying-to-hci-phds/#interviewing">Interviewing</a> section, we’ll discuss more about gauging advisor fit beyond just research interests, but for now, I think it’s important to focus on finding the right advisors to apply to based on research fit.</p><h3>Applying</h3><p>Once you’ve done your research and found the right programs and advisors, it’s time to start applying. I find this to be one of the more stressful and overwhelming parts of the process.</p><p>I got most of my applications written during Thanksgiving break, locked up in my apartment; I do not recommend this, and advise starting early (much earlier). I think the best way to approach this is to break it down into smaller tasks, and to start early. Use deadlines to your advantage, and set yourself a schedule to get everything done. At the end of my writing process, I had a few base essays, and swapped out paragraphs to fit each program.</p><p>It’s also important to have others read your essays, and to get feedback. It’s extremely easy to get caught up in your own writing, and to miss mistakes or areas that need improvement. I especially asked both research and non-research friends to read my essays, as they can provide different perspectives on your writing.</p><p>Also, don’t be afraid to revise your statements throughout the process; the applications I submitted in early November were very different from the ones I submitted in December. I think it’s important to keep revising and improving your statements until the very end, and to not be afraid to make big changes if necessary. (I rewrote one of my personal statements the night it was due, and I think it is one of my favorite pieces of writing I’ve ever done.)</p><p>If you’re like me, word count can be a challenge: there is always have more to say. However, it’s much easier to cut content than to add it, even if it feels like cutting is painful. I found that the best way to meet word counts was to focus on the core message I wanted to convey, and to deliberately cut out any content that didn’t contribute to that message. This is hard to learn, and something I only really got good at towards the end of my application process, but I think it’s a valuable skill to have.</p><p><em>My first application and last application had the same word counts, but I was able to fit a whole other paragraph/idea into the last one, and I think it was a much stronger application as a result. Cutting helps!</em></p><h3>Letters of recommendation</h3><p>Letters of recommendation are a crucial part of your application, and they can make or break your chances of getting into a program, as much as I hate to say it.</p><p>In the 2024 <a href="https://youtu.be/SRciEtSaBYs?si=8Hxf_AMp1KmQjCvR&amp;t=1174">PhD in Technical HCI Office Hours</a>, Dr. Michael Nebeling said:</p><blockquote><em>…the first thing I open is the letters of recommendation…I’m looking for signals [from] trusted colleagues…</em></blockquote><p>And I agree; when you ask someone to write you a letter of recommendation, you’re asking them to vouch for you and your abilities. So be considerate and ask people who know you well, and who can speak to your abilities and potential as a researcher. Programs typically expect three letters of recommendation; I had chosen two research advisors from UW, a professor collaborator from UMich, and my REU advisor from CMU. Why four? I was applying to different programs (CS, HCI, Informatics), and wanted to have a variety of perspectives on my work and abilities. (You don’t need four.)</p><p>It’s important that you ask your recommenders early, and give them enough time to write a good letter. It is also entirely okay if they say no; not everyone has the time or capacity to write a letter for you, and that’s okay. I asked my recommenders in August, and they had time until November-ish to write their letters. This gave them plenty of time to write a good letter, and to ask me any questions they had. Some of the resources I sent them were:</p><ul><li>My CV/Resume</li><li>A “brag sheet” with my accomplishments and experiences</li><li>A list of programs I was applying to, and the deadlines</li><li>My (draft) statement of purpose</li></ul><p>I really appreciate my recommenders for taking the time to write me a letter, and I find it important to show your appreciation for their time and effort once you’ve made your decision, or when major moments happen.</p><h3>Statement of purpose</h3><p>Your statement of purpose is your chance to do a few things:</p><ul><li>Describe your research journey</li><li>Explain your research interests</li><li>Show your passion for research</li><li>Demonstrate your fit for the program and advisor</li></ul><p>It’s hard to get started; what do you write about? How do you structure it? It’s easy to relegate this to be listing off your publications, but I think it’s more important to focus on your research journey. Personally, I found <a href="https://lucylai.com/blog/gradapps.html#the-statement-of-purpose">Dr. Lucy Lai’s “All About PhD Applications”</a> to be an amazingly helpful resource on the first draft of my statement of purpose.</p><p>My first draft was, (as most are) a mess. One of my recommenders, provided some amazing feedback on my first draft, and gave advice that I think is applicable to anyone writing their statement of purpose:</p><blockquote><em>You want to demonstrate that you don’t just have a general interest but also an idea for how to make a difference in that context. Show me how you’re thinking about research and are breaking down a larger problem…add a reference/citation to [your claims], you want to showcase that you know how to substantiate your claims/statements by citing relevant sources/evidence…</em></blockquote><p>These comments helped me focus on the core parts of my statement of purpose, and to really think about what I wanted to say. It’s about building to your research focus, based on the experiences you’ve had and the research you’ve done.</p><p>One hack I found was to use footnotes to add additional context or citations without cluttering the main text. (It doesn’t add to the word count, and it can be a great way to show your research depth without overwhelming the reader.) I believe I had eight footnotes in my final statement of purpose, which helped provide additional context and references without cluttering the main text.</p><p>Further than this, they also brought up a great point about writing towards programs, advisors, and their research groups:</p><blockquote><em>…what will you bring to [their] group/projects? What’s your value add?</em></blockquote><p>And this is really important; you not only want to learn and take during your PhD, but you also want to contribute and add value to the research group. This is a two-way street, and it’s important to show that you’re not just looking for a place to do research, but help foster a collaborative and productive research environment for future students.</p><p>It’s also really easy to get bogged down in word choice and sentence structure. I remember this stressing me out a lot, until one of my professors told me, “Ritesh, a word or sentence isn’t going to make or break your application.” And she’s right; while it’s important to have a well-written statement of purpose, it’s more important to focus on the content and the message you’re trying to convey.</p><p><em>(I did make a few tiny and not-so-tiny typos/mistakes in my final application, but I think the content and message were strong enough to outweigh those mistakes.)</em></p><h3>Your personal statement</h3><p>A statement of purpose and a personal statement are often conflated, but they are very different. Simply, a statement of purpose is “Why a PhD?” and a personal statement is “Who are you?”. There’s bound to be some overlap, but I think it’s important to keep these two separate in your mind.</p><p>I used my personal statement to go more into myself, and talking about my background, my experiences, and how they shaped me as a person and a researcher. I also used it to talk about my values, my passions, and what drives me.</p><p>It’s important to know that none of these statements exist in a vacuum; they are all interconnected, and they should all work together to tell a cohesive story about you as a researcher and a person. I think it’s important to have a clear narrative that ties everything together, and to show how your experiences and values have shaped your research interests and goals.</p><h3>Your diversity statement</h3><p>Some schools might ask you for a diversity statement; depending on the program, this may be the same as your personal statement, or it may be a separate essay. For some programs, my diversity statement was a separate essay, while for others, it was part of my personal statement.</p><p>Nonetheless, the diversity statement is your chance to talk about how you might add to the diversity of the program and the field as a whole. This could include your background, experiences, and perspectives that you bring to the table. As mentioned, this sounds pretty similar to the personal statement, but has a more narrowed focus on diversity.</p><h3>Your Resume/CV</h3><p>Your CV should be a comprehensive list of your experiences, accomplishments, and skills. It should include your education, research experience, publications, presentations, awards, and any other relevant experiences. It’s much different than applying for a job; you want your CV to be a historical record of what you have done. The existence of the CV is why your statement of purpose and personal statement should not be a list of your accomplishments.</p><p>Throughout college, I had started with a Word-based resume, but transitioned to the LaTeX-based <a href="https://www.overleaf.com/latex/templates/jakes-resume/syzfjbzwjncs">Jake’s Resume Template</a>. And I found that the LaTeX format allows for much greater flexibility, especially with a CV being a bit different than a resume. But it is pretty easy to adapt the template to your needs, and I think it’s a great starting point.</p><p>You can view <a href="https://riteshkanchi.com/resume">my resume</a> for reference, but I think it’s important to focus on the content and the structure of your CV, rather than the specific format. You want to make sure that your CV is easy to read, and that it highlights your most relevant experiences and accomplishments.</p><p>It’s also extremely important that you ensure that your CV is accessible. Some professors might ask you to submit your CV in an accessible format (or more specifically, screen reader-friendly), and personally, I don’t find LaTeX-based PDFs to be very accessible. For these cases, I converted my resume into a linear, list-based Word document which is much more accessible.</p><h3>Recovery</h3><p>There are a few sections in this post about recovering from each part of the process, but I think it’s important to take a step back and reflect on the process as a whole. By December 15th-ish, I had submitted all of my applications, and I was exhausted. Luckily, you have a few weeks to recover before you get into the next part of the process: interviewing. Recovery should be focused on taking a break, and reflecting on what you wrote (or not!). There’s nothing more you can do at this point, and it’s important to take a step back and relax.</p><h3>Interviewing</h3><p>Now that it’s the new year, you’re (hopefully) in the interview stage of the application process. This is an exciting time, but it can also be nerve-wracking. You’ll be recieving emails from faculty who are interested in interviewing you, and these are just as important as the applications themselves. Recieving an interview means that you are a strong candidate, your application met the bar, and that faculty are interested in learning more about you. The shortest interview I had was 30 minutes, and the longest was around 3 hours.</p><p>Your application, letters of recommendation, and CV/supplemental conent have all been reviewed, and now it’s time for you and them to get to know each other better.</p><h3>Preparation</h3><p>Some faculty might say, “Please read one of my papers before the interview,” and some might tell you to come without any specific preparation. Either or, I found it really important to prepare deeply for the interview. I kept a notebook with each faculty member I was interviewing with, and wrote down the following:</p><ul><li>What I wrote about them in my application</li><li>What their website and research interests were</li><li>What their recent publications were</li><li>A brief summary of a paper or two that I found interesting</li><li>Questions I had about their papers, them, or their research group/program</li></ul><p>This might seem like overkill, but it made it extremely helpful to read over my notes before the interview, and to have a clear idea of what I wanted to ask and talk about. I also took notes briefly during the interview, which helped me remember what we talked about and what I wanted to follow up on later, either at the end of interview or over email.</p><p>But as another point, I found this really helpful to learn about the breadth of HCI research in my specific-subfield, and to see how different faculty approached similar problems in different ways. This is a great way to learn about the field as a whole, and to see how your research interests fit into the larger picture.</p><p>I also recommend having some research project ideas in mind, and being able to articulate them clearly. This doesn’t mean you need to have a fully fleshed out research proposal, but having a few ideas that you’re passionate about can help you stand out in the interview process. It also shows that you’re thinking about your research interests and how they align with the faculty’s work.</p><h3>What to expect</h3><p>The interview process can vary widely depending on the program and faculty, but I think there are a few common themes that I found in my interviews:</p><ul><li>Discussing your application and research interests</li><li>Asking you to describe a project or paper you’ve worked on</li><li>Describing a hypothetical research project or problem, and asking how you would approach it</li><li>Asking you about your long-term research goals and interests</li></ul><p>There are a lot more questions that you might be asked, but I think these are the most common ones. It’s important to be prepared to talk about your research interests and experiences, and to be able to articulate your long-term goals and interests.</p><p>For one of my interviews, I had spoken with four current students and then the faculty member for about 3 hours total. While a lot, I appreciated the diversity of questions I was asked, and the opportunity to get to know the faculty member and their research group better.</p><p>In general, all of my interviews were very conversational, and I felt like I was able to get to know the faculty members and their research groups better. I wasn’t particularly stressed or nervous in them, and they tended to be somewhat casual and informal. I think this is a good sign that the faculty are interested in getting to know you as a person and a researcher, and that they want to see if you’re a good fit for their research group.</p><h3>What to look for and ask</h3><p>But being asked questions is only half of the interview; you should also be asking questions. Use this opporunity to ask questions about things you care about, and to learn more about the faculty member and their research group. Some questions I found helpful to ask were:</p><ul><li>Why did you choose to work at this university? Why have you stayed?</li><li>What do you wish you could work on, but don’t have the time or resources for?</li><li>What is your advising style like? How has it changed?</li><li>What are your expectations for your students?</li><li>What is the culture of your research group like?</li><li>What excites you about your current research?</li></ul><p>There are dozens of questions you could ask, but I think it’s important to focus on the ones that are most relevant to you and your research. This is your chance to learn more about the faculty member and their research group; you want to gauge their “vibe” (for lack of a better term), and to see if you would enjoy working with them for the next 5+ years. It’s also important to not get your hopes up too high: you don’t have an offer yet.</p><p>I had one interview that went extremely well, and I felt like I had a great connection with the faculty member. But I ended up not getting an offer from that program; it was disappointing. But the faculty member emailed me, saying that they enjoyed our conversation but believed they wouldn’t be able to provide the support I needed, and referred me to another faculty member who they thought would be a better fit. This was a great example of how the interview process can be a two-way street, and how it’s important to find the right fit for both you and the faculty member.</p><h3>Recovery</h3><p>Interviews are exhausting, especially when you interview with multiple faculty members in a single day, or across various time zones (I had 6am and 8pm interviews!). Again, it’s important to take a step back and reflect on the process as a whole. After each interview, I wrote down my thoughts on the interview, for (hopefully) future reference. You will talk to many different faculty members, learn a lot, and get a lot of different perspectives on your research interests and goals. It’s important to take the time to reflect on what you’ve learned, and to think about how it fits into your overall research journey.</p><h3>Deciding</h3><p>So. You’ve applied, interviewed, and now you’re waiting for the decisions to come in. This section is about how to decide on the right program, advisor, funding, and research focus for you; especially if you have multiple offers.</p><p>First, congratulations! This is a huge accomplishment, and you should be proud of yourself for making it this far. But now comes the hard part: deciding on the right program for you. Over the next month or so, you’ll hopefully have the opportunity to visit the programs you’re interested in, and to meet with your prospective advisors and labmates. This is a great opportunity to learn more about the program, the faculty, and the research group, and to see if it’s a good fit for you.</p><h3>Talking to prospective advisors</h3><p>If you have the chance to talk with the advisor(s) before you travel to learn about the program, I suggest taking it. You’re now in a different position, and can ask more specific questions about them, and the program. While you will learn a lot from your time visiting campus(es), getting the basics down will help you immensely. Take notes! You will be juggling many terms, lingo, and documents, and staying organized is key when comparing offers.</p><p><em>In the current political climate, it is 100% safe to ask in-depth about current and future funding. I do not advise you to self-fund a PhD.</em></p><p>There’s also the value of trust; one of these advisors will be yours. I personally was honest about this with all of my prospective advisors, but your mileage may vary. I appreciated that each advisor told me that while they wanted me to join their group, they also cared about me finding the best fit, even if not with them.</p><h3>Questions to ask</h3><p>There are a few things you should be considering when making your decision, and the questions you ask now are much different than the ones you asked during your interview. I really liked <a href="https://blog.ml.cmu.edu/2020/03/02/questions-to-ask-a-prospective-ph-d-advisor-on-visit-day-with-thorough-and-forthright-explanations/">Andrew Kuznetsov’s blog post</a> on Questions to Ask a Prospective Ph.D. Advisor; I agree with every question here, and think if you can, try to get them all answered. You can also ask some of these questions to prospective labmates, who may give you a more objective answer in some cases.</p><p>Talk to as many people as possible! Talk to other prospective students, adjacent faculty, and other PhD students outside of your lab. Everyone has differing opinions, and can help inform yours best. (It might be a lot, but you’ll appreciate it in the end.)</p><p>If such a case, try talking to students who had left the lab. You can ask prospective labmates to see if you can talk to the former labmate and learn what was the reason they left. It’s not always the lab itself, but sometimes the student’s research interests. The best thing you can do is try and get as broad of a perspective as possible during this experience.</p><h3>Making the decision</h3><p>Sometimes making the decision is dead simple. If it is, you’re done!</p><p>But other times, it’s tough. You have a few programs that are really tied up, and you’re having a difficult time trying to decide. First of all, sometimes, there is no wrong choice. Multiple programs might make you a great researcher. But you need to start doing tiebreakers. Here are some factors to consider:</p><ul><li>Lab Culture</li><li>Research</li><li>Institution</li><li>Funding/Cost of Living (extremely important)</li><li>Location/Weather</li><li>Vibes (for lack of a better term)</li></ul><p>Once you’ve made your decision, you should email your accepted advisor to inform them of the decision. You should also email your rejected advisors to inform them as well. Be brief in this email, but considerate and appreciative. It may be bittersweet, but this doesn’t mean your relationship is entirely over. You might see them again in the future at a conference, workshop, or event! (One of the programs I visited had a “How to reject offers” seminar which I found extremely helpful…)</p><h3>My final results</h3><p>I thought I’d share my own PhD application journey. I applied to 10 programs, and when it came down to my two offers, it truly was a difficult decision. I appreciated both programs, and I had a great connection with both faculty members. What I learned was that faculty are there to not only convince you to join their program, but also to help you find the right fit for you, even if it is not with them. Both faculty members were extremely supportive, and they wanted what was best for me.</p><p>I had a rough time deciding between both of my offers; they were both phenomenal, and dream offers I never thought I would get. In the end, I’m very happy with the decision I made.</p><figure><img alt="A Sankey diagram showing my PhD application process: 10 applications, 6 interviews, 1 waitlist, 8 rejections, 2 offers, 1 accepted offer, and 1 declined offer." src="https://cdn-images-1.medium.com/max/1024/1*pHhWcxFBWCBNeWifHeUXWw.png" /></figure><p>At the end of the day, it is your decision; and as said, sometimes, there is no wrong choice.</p><h3>Thank You</h3><p>Phew! That was a lot of information, and I hope it was helpful. I know that applying to a PhD program can be a daunting process, but you have a lot of resources available to you, and I hope that this post can be a helpful starting point. I want to thank all of my professors and advisors who helped me through the application process, providing me with extremely helpful feedback and advice.</p><p>If you have any thoughts or questions, please feel free to reach out; I would be more than happy to help or update this post.</p><p>9/18/26: Thank you to Anissa Patel for catching typos.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7422f490fef1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Making of the all-new STEMpump App]]></title>
            <link>https://riteshkanchi.medium.com/the-making-of-the-all-new-stempump-app-ce17b03e71be?source=rss-5a56cf738ae6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce17b03e71be</guid>
            <category><![CDATA[nonprofit-technology]]></category>
            <category><![CDATA[high-school]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Ritesh Kanchi]]></dc:creator>
            <pubDate>Thu, 17 Mar 2022 05:24:26 GMT</pubDate>
            <atom:updated>2026-03-03T04:19:49.594Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Making of The all-new STEMpump App</h3><h4>How do we design and develop a new experience for students to learn? An introspection into the development of the all-new STEMpump app.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kx2FSziF0Kk6oztbsbz-9w.png" /></figure><blockquote>2026 Update: Excuse the naivety of the writing; I hadn’t gone to college yet, haha. Much of what I say here, I now either: (a) disagree with, or (b) now have the proper terminology for.</blockquote><p>It&#39;s been, well, a while. I previously wrote <a href="https://riteshkanchi.medium.com/the-making-of-the-stempump-app-da452a95fbd0">this post</a>, which briefly highlighted my journey of developing my first app, STEMpump. And while I planned to write more posts about the versions to follow, I didn&#39;t feel like there was enough to write about. As a result, I have a few semi-done drafts that might never see the light of day because nothing was that big of an improvement or innovation to write about.</p><p>If anything, this post indicates massive improvements and innovation since my first app. This post is a &quot;brief&quot; summarization of the theory, technology, and implementation that went into the latest STEMpump app, which might be a whole different thing. You can download the app for yourself <a href="https://stempump.org/">here</a>.</p><h3>What is STEMpump?</h3><figure><img alt="STEMpump" src="https://cdn-images-1.medium.com/max/1024/1*p05mCJZTeLMTfoLqGd6feQ.png" /><figcaption>The STEMpump Logo</figcaption></figure><p>Before we jump into the technojargon, you might not know what STEMpump is if you&#39;re new.</p><p><a href="https://stempump.org/">STEMpump</a> is an educational organization dedicated to creating a global platform for contribution, collaboration, and expression. We aim to transform traditional education by offering a modernized teaching environment that gives students a medium to learn and contribute to our mission of free education for all.</p><p>As students, we create free, accessible educational technology and content for students, all of which are STEAM-based. (STEAM: Science, Technology, Engineering, Arts, and Math; yes, I know we&#39;re called STEMpump, not <a href="https://steampump.org/">STEAMpump</a>.)</p><p>We do everything in-house, from our visual media to our live streams, even our entire publishing backend. So I&#39;ve learned about building industry-level technologies while working towards a fantastic cause — free education for all.</p><p>We&#39;ve taught over 110K+ students from 110+ countries, and we&#39;re not stopping soon. Our mission statement is our goal, and this app is a stepping stone to that point.</p><h3>Who are you?</h3><p>My name is Ritesh Kanchi. I&#39;m a high-schooler interested in Human-Computer Interaction, Social Impact, and Educational Technology.</p><p>I write about my experiences and thoughts on technology, art, and education. I also create cool things from time to time. You can follow me on <a href="https://twitter.com/rtsh__">Twitter</a> or <a href="/service/mailto:ritesh@stempump.com?subject=Contact">shoot me an email</a> if you want to chat.</p><p>Anyways, let&#39;s jump right into it.</p><p>I&#39;ve broken this post into two main sections, with a few subsections: <strong>Design</strong> and <strong>Development</strong>. I like to break up all my projects like this, as it gives me an individual focus at a time, so it only makes sense to write in the same standard.</p><h3>Design</h3><h4>Content to Read from vs. Content to Learn from</h4><figure><img alt="The app from April 2021 that’s Version 3, and the app from March 2022 that’s Version 4" src="https://cdn-images-1.medium.com/max/1024/1*CvghjmXGLXvB6qkvbTdmRQ.png" /><figcaption>What a difference — you can actually learn from one of these!</figcaption></figure><p>There&#39;s a big difference in how content is perceived. Whether it&#39;s a lesson, blog post, transcript, glossary, whatever, it&#39;s not something I mainly understood over the first three versions of this app.</p><p>See, it&#39;s easy to &quot;randomly&quot; stylize some content, throw it on a view/screen, and call it a day. It&#39;s effortless to do so — and for a good reason. In this context, we have <strong>Content to Read from</strong>. You read it, and you&#39;re done. In the real world, menus, instructions, and signs are forms of this. We&#39;re not meant to learn; we just choose and follow.</p><p>What&#39;s harder is creating <strong>Content to Learn from.</strong> How we display typography, blocked elements, etc., directly influences how we learn. Text isn&#39;t over or under stylized, but just enough so that we can remember it. This includes some modern textbooks, online documentation, and simple tutorials. Flashcards, unsurprisingly, also fall under this. (Have you found anyone who learns from terribly/overly designed flashcards? I didn&#39;t think so.)</p><blockquote><a href="https://www.lexend.com/">While we didn’t use it, Lexend is an amazing font system that&#39;s truly working to change the way we read/learn from typography.</a></blockquote><p>Last summer, we updated our Typography styling on <a href="https://stempump.org/">STEMpump.org</a> when we shifted our whole platform to the JAMStack. <a href="https://tailwindcss.com/blog/tailwindcss-typography">Tailwind Typography </a>is a great base, and we built on top of it to meet our needs.</p><p>At STEMpump, we primarily write our content in <a href="https://daringfireball.net/projects/markdown/">Markdown</a>, and for the app, we used <a href="https://github.com/johnxnguyen/Down">Down</a>, a &quot;Blazing fast Markdown rendering system&quot; to render it out with Swift.</p><figure><img alt="Syntax Highlighting, Syntax File Naming, Accessible Text" src="https://cdn-images-1.medium.com/max/1024/1*WQ9ZZfOGnBVDpg-IUqZIug.png" /><figcaption>Extended functionality: Syntax Highlighting, Syntax File Naming, Image Alt. Text</figcaption></figure><p>However, we were limited by Down and its inability to add new rules and extensions to the parsing system. To bring over features such as Syntax Highlighting, Syntax File Naming, and Image Alternative Text, I wrote a simpler Markdown parser that adds everything missing. It&#39;s high efficiency, meaning that Down can still be fast enough to render massive amounts of content in milliseconds.</p><h4>Designing towards Accessibility: Universal Design</h4><p>There&#39;s been a massive design trend with accessibility in mind in recent years. Not only being able to make products for all to use but provide the same experience.</p><p>I spent the Fall on a deep dive into Universal Design and accessibility. I&#39;ve read opinions that said Universal Design just couldn&#39;t exist but also views that it exists everywhere.</p><blockquote>Universal design is the design of buildings, products or environments to make them accessible to all people, regardless of age, disability or other factors.</blockquote><p>With that in mind, it&#39;s an exciting idea:<strong> design for everyone?</strong> It seems impossible.</p><p>But here&#39;s my stance: &quot;Yes, it&#39;s impossible-that doesn&#39;t mean we shouldn&#39;t try to make it possible.&quot; Everything is always impossible before its possible, isn&#39;t it? <a href="https://www.news.com.au/technology/innovation/inventions/the-life-changing-inventions-the-experts-said-were-impossible/news-story/8c8b0e58532b329d1b6f97c3dfee9fcc">(i.e., space flight, the lightbulb, personal computing)</a></p><p>I also thought a bit about the idea of majority vs. minority design and have the conclusion:</p><blockquote>“An interesting thing happens when we design for the minority first.</blockquote><blockquote>I believe when you design with the minority in mind, the majority will benefit. They benefit via the concept of universal design: design that is accessible to all people. So the real question is, how do we go about designing for the minority? How do we redefine technology with no significant group in mind?”</blockquote><blockquote>- Me, 2021</blockquote><p>And there&#39;s a good reason I leave it open-ended: because the answer to this question changes on a person-by-person basis.</p><p>So when it comes to accessibility in this app, how did I approach it? Well, slow and steady wins the race, right? I had the opportunity in December to speak to Apple Engineers about accessibility in the V3 app, and the majority of suggestions they offered are now implemented in the app.</p><p>One of the big ones was that our Markdown content now scales with <a href="https://developer.apple.com/documentation/uikit/uifont/scaling_fonts_automatically">DynamicType</a>, which didn&#39;t happen before. The app is now more linear for automatic accessibility functions to be much better than prior versions.</p><p>Accessibility in design remains our number one priority, and it won&#39;t leave that spot — we can <strong>always</strong> make technology more accessible. We can <strong>always</strong> make experiences more universal.</p><h4>Defining a new, cross-platform Design System</h4><p>Last summer, we moved our entire web platform to the JAMStack. This required a total rewrite from the ground up with React and <a href="https://nextjs.org/">Next.js</a>. With <a href="https://tailwindcss.com/">TailwindCSS</a>, we were given the power of a utility-first CSS framework to redefine what we wanted STEMpump to feel like.</p><figure><img alt="PacificUI logo" src="https://cdn-images-1.medium.com/max/1024/1*zmhLJFxYyeJ9OvtvRUkuGA.png" /><figcaption>PacificUI Logo</figcaption></figure><p>We designed <strong>PacificUI 2</strong>, our in-house design system, as a conglomeration of modern design and our organization&#39;s past. As a result, our design sense was simplified and placed a stronger emphasis on learning.</p><p>So when it came time to develop the app, we had to redefine PacificUI to look just as good on both the web and mobile. The app has elements lifted directly from the site while maintaining its unique look. With a lot of the views in the app, I hope to bring the same level of design to the website, as are complementary experiences.</p><p>It&#39;s always been the case where the app&#39;s functionality surpasses the website, but as we continue developing both side by side, that gap seems to be decreasing to reach a 1:1 parity (almost.)</p><figure><img alt="Four phones in dark mode displaying varying STEMpump content" src="https://cdn-images-1.medium.com/max/1024/1*H9XtukL2pU2WarKSaL5Efw.png" /></figure><p>Making a new Dark Mode was an exciting challenge. I learned that pure black interfaces aren&#39;t always the best choice —<a href="https://www.editorx.com/shaping-design/article/designing-for-dark-mode"> but almost black interfaces are.</a> They make things feel cleaner and make the experience feel almost bounded. We still use pure black in some places, but for the majority of the app, you&#39;ll get the &quot;off-black.&quot;</p><p>Same with the Light Mode, we&#39;re using an &quot;off-white,&quot; which presents the same feeling with the Dark Mode. And I think it comes down to imperfection. But it also is about bringing depth to our design, something we can do with these variants.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FVURsqm49Sqe9G%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fthelegomovie-lego-the-movie-VURsqm49Sqe9G&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2FVURsqm49Sqe9G%2Fgiphy.gif%3Fcid%3D790b7611c50021f4dcddc799f709a891260011245c3efc48%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="180" frameborder="0" scrolling="no"><a href="https://medium.com/media/2be5d8dda3057b5c7acc9825fa2210bc/href">https://medium.com/media/2be5d8dda3057b5c7acc9825fa2210bc/href</a></iframe><h4>Layout/Responsive Hell</h4><p>I&#39;m going to be honest; I&#39;m no <a href="https://www.google.com/search?q=marie+kondo&amp;oq=Marie+Kondo&amp;aqs=chrome.0.0i355i433i512j46i433i512j0i20i263i512j0i433i512j46i433i512j0i512l5.115j0j7&amp;sourceid=chrome&amp;ie=UTF-8">Marie Kondo</a>. So when it came to the layout and organization of this app, it was almost a nightmare for the first few iterations. As I write this, I redesigned the interface of courses yesterday — that&#39;s how unconfident I was in the old design.</p><p>Being in a fixed space such as a phone is great! I love restrictions and rules in design because it forces me to &quot;color inside the lines.&quot; More problem-solving is required to get everything to fit. We&#39;re now using a tabbed bar to divide the app into five views: <strong>Discover, Courses, Camps, Favorites, </strong>and <strong>Search</strong>. It makes things easier for the user and gives you fingers reach to everything.</p><p>I&#39;m a sucker for something called <a href="https://addyosmani.com/blog/touch-friendly-design/"><strong>The Thumb/Touch Zone</strong></a><strong>.</strong> Essentially, the idea is that our hand is forced to stretch further across the screen proportionally to the size of our phones over time. (Remember the original iPhone? Now look at the iPhone 13 Pro Max — crazy.)</p><figure><img alt="The Thumb Zone; OW: Hard to reach, STRETCH: Inconvenient to reach, NATURAL: Comfortable to reach" src="https://cdn-images-1.medium.com/max/1024/0*jsk5eZa4fqfXmF_X.png" /><figcaption>The Thumb Zone</figcaption></figure><p>This idea doesn&#39;t mean we should avoid the <strong>Ow</strong> or <strong>Stretch</strong> areas — it just means we need to be deliberate about where we place functionality. For example, the Tabbar, synonymous with many iOS apps, made the most sense as a point of the main traversal through the app.</p><p>And we have a custom navigation bar on most views to enable tapping the back button. Finally, we added a new swipe back feature, one that&#39;s seen in most apps, allowing you to drag the view from the leading edge to go back. Our previous versions didn&#39;t have exemplary implementations, but the new one is pretty nice. Moreover, it&#39;s modular, giving us full extendability.</p><figure><img alt="Navigation Bar shown on the bottom of the image, Tabbed Bar at the top of the image" src="https://cdn-images-1.medium.com/max/1024/1*6Mq-cyFHUh07Ue5RX_ovmA.png" /><figcaption>Examples of our Navigation and Tabbed Bars</figcaption></figure><p>But what&#39;s hard? <strong>Designing for iPad.</strong> When it comes to SwiftUI and its ability to work on multiple Apple platforms, it&#39;s, uhh, below average. Also, if you do anything custom, the iPad freaks out a bit due to the larger size or adds things we don&#39;t want.</p><p>For now, we are shipping a very basic iPad app with V4.0.0. But by 4.1.0, there will be much better refinement for iPads. That&#39;s just how it is — it works, but we can always do better. The app we&#39;re shipping is still miles better than whatever the iPad currently has.</p><h4>Have fun with Design</h4><p>A big thing about Design is showing your personality and making it personal. I found a few ways to show this off, with two things primarily.</p><figure><img alt="A phone shaking with STEMpump Dice" src="https://cdn-images-1.medium.com/max/1024/1*Jvld5l_mgxubboIQvJpOkg.png" /><figcaption>STEMpump Dice!</figcaption></figure><p>On <a href="https://stempump.org/">STEMpump.org</a>, we added a new experience called <a href="https://stempump.org/dice"><strong>Dice</strong></a>. It&#39;s a simple content randomizer that finds you a camp or course and just redirects you into it. It&#39;s a fun thing with a few animations.</p><p>So with the app, when I thought we could do it, I had zero hesitation. Dice is now on the Courses tab, and you can click it, and it&#39;ll perform with the same functionality as the site. I also got to write a new cross-platform API for this functionality.</p><p>But here&#39;s where the fun part comes in: the randomizer will also work when you shake your device! Kind of<em> like real dice. </em>Just shake it, and it&#39;ll randomize!</p><blockquote><strong><em>PSA: Do not use your iPhone or iPad as a real dice!</em></strong></blockquote><p>Another fun thing I got to do was the Welcome Screen for new users. We&#39;ve never done this before, so I wanted to do something unique.</p><figure><img alt="A welcome screen with animated course work" src="https://cdn-images-1.medium.com/max/1024/1*gSPC8pa5jYeOEloPLga4nQ.gif" /><figcaption>The brand new welcome screen for STEMpump!</figcaption></figure><p>This new Welcome Screen displays a grid of our course and camp artwork infinitely scrolling, along with a few stylized gradients and text below. Creating the infinite art grid was interesting.</p><p>In <a href="https://figma.com/">Figma</a>, I set up a frame with the grid inside, with the starting and ending tiles being the same. With a fantastic motion design tool called <a href="https://jitter.video/files/">Jitter</a>, we can take the frame from Figma and animate it. I lined up the starting and ending positions, exported the video, and added a view to display it.</p><p>And it turned out awesome! It&#39;s stylish, functional, and shows what STEMpump has to offer.</p><h4>Tools of the Trade</h4><p>As we wrap up this section, I thought I&#39;d go over the tools I used for design. Whereas I used Adobe XD in the past, it was not as flexible as I&#39;d like. Adobe programs haven&#39;t been something I&#39;ve enjoyed using because of their strain on processing and terrible experience.</p><figure><img alt="A flowchart with different paths mimicking userflow and data flow" src="https://cdn-images-1.medium.com/max/1024/1*T7r6TdUltDThR0vuVoaJGg.png" /><figcaption>Figjam with a very barebones, early-stage version of the current overview/userflow</figcaption></figure><p><a href="https://figma.com/">Figma</a> has been my savior throughout this process — something we&#39;ve used from Day 1 to Day ???. We used <a href="https://www.figma.com/figjam/">Figjam</a> to plan out user flows, view organization, and how functionality and different networking pipelines would work.</p><p>Then we used Figma itself to plan out views themselves, create components of our mobile views, and experiment with different layouts and styles. Figma is becoming an all-in-one tool, and I&#39;m all for it.</p><p>I could go on and on about design theory and superb design examples in our app, but this post would never end! Instead, I hope to write more often about design in the future, so keep on the lookout for that.</p><h3>Development</h3><p>Design is only one half of the story itself. How something is developed to complement the design or how the function influences the design (and vice-versa) matters.</p><h4>The power of SwiftUI</h4><p>As mentioned, we&#39;ve written our app primarily in SwiftUI. We have a few UIKit extra functionalities, but for the most part, we&#39;re using SwiftUI.</p><figure><img alt="Macbook, iPad, and iPhone with the same app" src="https://cdn-images-1.medium.com/max/1024/0*jVrCSantjKJvZBY8.png" /><figcaption>SwiftUI in its cross-platform glory…</figcaption></figure><p>And if anything, it&#39;s been a really good time building in it. For some functionality (like the Quizzes now in the app), I just rewrote our JSX in Swift, and the functionality just worked!</p><p>React and SwiftUI are pretty similar for handling components and views, making the jump back and forth pretty good.</p><p>We built this app for iOS 15, so it takes advantage of many built-in features and many of the features that matured since iOS14. For example, we&#39;re now using Lazy stacks for network data to better performance and efficiency and decrease device load.</p><p>We&#39;re now using AsyncImage for image displaying, the new Material backgrounds, asynchronous tasks, and @StateObject To name a few. The general trend is that Apple will ship more things from UIKit to SwiftUI every year, and I&#39;m all for it — as long as they make it easier to work with iPad.</p><h4><strong>A whole new type of CMS: Sanity.io</strong></h4><p>During the summer JAMStack transition, finding a new content management and storage provider was a big goal. We had to make sure that content from STEMpump would load and update quickly, anywhere in the world. The worst thing a student can have is terrible load times.</p><p>We found <a href="https://sanity.io/">Sanity.io</a>, a unified content platform that powers experiences from companies such as Netlify, Nike, Sonos, Figma, and now, STEMpump. While most CMSs are designed for a singular platform, the web, Sanity.io, is appealing as a unified content platform: it works on various platforms.</p><figure><img alt="Code Editor with Sanity.io CMS next to it" src="https://cdn-images-1.medium.com/max/1024/0*3tHuMHgItouwLkTn.png" /><figcaption>How it looks like to work with Sanity.io</figcaption></figure><p>However, they don&#39;t have a well-developed Swift counterpart yet, making it hard to request data. On top of that, they use their querying language: <strong>GROQ (Graph-Relational Object Queries)</strong></p><p><strong>I love GROQ.</strong> When I go back to GraphQL now and then, I wish it was written in GROQ. It&#39;s intuitive, helpful, and more precise than GraphQL. I can get the data I need, not the data I don&#39;t.</p><h3>Ritesh Kanchi on Twitter: &quot;thanks @sanity_io for making me love groq and hate graphql 🥲 / Twitter&quot;</h3><p>thanks @sanity_io for making me love groq and hate graphql 🥲</p><p>But like I said, there&#39;s no well-developed Swift counterpart — but they do have a query URL system, which is precisely what was needed to make our own. So we can write GROQ, then URL encode it, and request data from our Sanity.io CMS in our app. It&#39;s pretty simple, actually, but it gets the job done.</p><p>But also, what makes Sanity.io even more awesome (I know, right) is that it offers both Asset and API CDNs — giving us fast responses to requests that are cached. We use the Asset CDN for all files and graphics in the app but use the API CDN and the uncached API intermixed based on the functionality.</p><p>Some things use the API CDN to load in data fast, like lessons and courses. Other things, like the Camp Live Card or Dice, use the uncached API to load updates as soon as possible, making sure everything is fresh.</p><p>We&#39;re also developing our APIs to query our CDN, giving us continued extendability of our Sanity.io CMS for functionality that needs to be modified or altered. And with Sanity.io&#39;s Google Cloud Platform backend, we can take advantage of dozens of GCP, such as BigQuery, Cloud DNS, and the Kubernetes Engine.</p><figure><img alt="Sanity Logo" src="https://cdn-images-1.medium.com/max/1024/0*-BG5GcGGsmMUkvR7" /></figure><p>The CDN Edge Network from Sanity.io powers all of STEMpump&#39;s experiences now and makes it easy for us to create new ones without any updates to the database. For example, not once did I need to update the CMS for the app, only when I wanted to add more fields and data.</p><h4>Realm: Everything CoreData wished it was</h4><p>In the prior release, V3, we implemented a new feature called <strong>Favorites</strong>. You could favorite courses, filter them, and that&#39;s about it. It did its job, and that&#39;s the good part.</p><p>But it used Apple&#39;s CoreData, and in a single emoji, here&#39;s how I would describe it: 🤮</p><p>It&#39;s rough to work with, hard to expand and not suited for modern-day apps. Enter <a href="https://realm.io/">Realm</a>.</p><figure><img alt="Realm by MongoDB Logo" src="https://cdn-images-1.medium.com/max/970/0*4yGNAN8-DqlFCt2F.png" /></figure><p>&quot;Realm&#39;s mobile database is an open-source, developer-friendly alternative to CoreData and SQLite. Start in minutes, port your app in hours, and save yourself weeks of work.&quot; — they did not lie. It&#39;s made by <a href="https://www.mongodb.com/">MongoDB</a> and has a remarkable Swift (and SwiftUI) implementation.</p><p>I was able to get Favoriting for courses done in under half an hour, and then Favorite Camps, Favorite Lessons, Continuity, and Registered Camps, done in the half-hour after. But, of course, all of this would&#39;ve been a total slog with CoreData.</p><p>It&#39;s literally as easy as this.</p><pre>import Foundation<br>import RealmSwift</pre><pre>class SavedNote: Object, ObjectKeyIdentifiable {<br> @Persisted(primaryKey: true) var id: ObjectId<br> @Persisted var name: String<br> @Persisted var content: String<br> @Persisted var date: Date<br> @Persisted var pinned: Bool<br>}</pre><p>With Realm, we can develop one of my favorite features: <strong>Continuity</strong>, aka<strong> Continue Learning</strong>.</p><figure><img alt="Continue Learning" src="https://cdn-images-1.medium.com/max/1024/1*NaP3VEo682GD6Jv3ccSa7g.png" /></figure><p>I originally had a feature similar to the previous version but ultimately had to scrap it due to functionality errors between CoreData and UserDefaults. That, and it only stored the most previous Course you viewed.</p><p>With Continuity in the all-new STEMpump, we&#39;re tracking the past ten lessons, projects, or quizzes you&#39;ve visited. We may leave this at ten, increase it, decrease it, or give the user the option. Continuity works like a charm, rearranging orders in itself based on the most recent content you&#39;ve viewed.</p><p>I was even able to extend its functionality, allowing students to jump straight into their last lesson, just from the course view — no need to search for it. But, unfortunately, it only exists for the items in Continuity, so if you looked at a course a while ago, it wouldn&#39;t show. We can extend this functionality, but it will require testing to see how large we can make the overall Realm array.</p><p>All in all, Realm is an excellent mobile database and offers some great functionality when it comes to creating classes, objects, and managers. I particularly loved @ObservedResults,as it gave everything I possibly wanted straight out of the box.</p><blockquote><a href="https://stempump.org/camps/lets-make-an-app-with-swiftui-and-realm-03-12-2022"><em>Realm is so great that I taught a camp on how to make a simple Notes app with Realm and SwiftUI.</em></a></blockquote><h4>How do we bridge the divide between web and native?</h4><p>I think it&#39;s an excellent question to ask and something that many people take for granted. Most popular and great experiences have web and native counterparts, but are they complementary or supplementary?</p><p>We hope that the app is a supplementary experience to the website for mobile, but we can&#39;t forgo all of our content for the web either. We need to focus on both platforms equally and ensure they have feature parity.</p><p>We use Markdown, which is a web-based markup language. We use modified WebViews to display it, along with the system accessibility functionality built-in. Is this native or web? I&#39;d argue it&#39;s a good mix of both, but problems still exist.</p><p>A few months ago, we received a lengthy review that highlighted many problems with the app&#39;s experience (Yes, we fixed every single one.)</p><p>One part stood out to me:</p><blockquote>“The article with suggested courses does not have any links to those courses.”</blockquote><p>At the time, I had no clue how we could fix this; We are displaying content in a WebView. We can send data, but receiving isn&#39;t that good. This is where the idea of STEMpump Bolt came.</p><p>Bolt is built on the same groundings of the Markdown parser I wrote but scans Markdown looking for STEMpump content. Right now, it only checks for courses, but I hope to expand its functionality. If it finds any content, it shows a suggestion to add it to your Favorites. In addition, it shows up in Lessons, Announcements, and Camps, which shows how easy it is to scale it across the app.</p><figure><img alt="Bolt scanning Markdown Content" src="https://cdn-images-1.medium.com/max/1024/1*xrlPlgvUVkg6eq9pASy_2w.png" /><figcaption>STEMpump Bolt in action</figcaption></figure><p>And in Favorites, Bolt-suggested courses are displayed with a special badge to differentiate content you favorited versus suggested content.</p><figure><img alt="See All: Favorite Courses, shows Bolt Courses" src="https://cdn-images-1.medium.com/max/1024/1*xaVKyYSYcbdwm7WnntGtLw.png" /><figcaption>How Bolt courses look</figcaption></figure><p>We were able to make sure we had feature parity by developing new, cross-platform APIs. These APIs control the Live Camp and Course of the Week data, Dice, Bolt, and how one registers for a camp.</p><p>I wrote a new API that accepts a POST Request from the app then sent a few different API calls to <a href="https://supabase.com/">Supabase</a>, <a href="https://www.mailgun.com/">Mailgun</a>, and <a href="https://posthook.io/">Posthook</a>. We use these services for STEMpump Camps, as it gives us the functionality we built over the Winter to create an incredible registration process.</p><p>Initially, the idea was to have a simple WebView that displayed a modified version of our camp registration; it became challenging, especially since we wanted to show the camps the user signed up for. This new API granted us the ability to save the camp to Realm and send data to a single source.</p><p>The end experience is excellent — just enter your info, boom, you&#39;re done. You&#39;ll get an email confirmation and a reminder 3 hours before your camp.</p><figure><img alt="Camp Registration userflow" src="https://cdn-images-1.medium.com/max/1024/1*arx2yg8Ua7BAAqs09bmFIg.png" /><figcaption>Camp Registration made easy</figcaption></figure><p>As time goes on, expect the gap between the web and native experiences to shrink to the point where either option is great to discover something new.</p><h4>Search that&#39;s Human</h4><p>We also adopted <a href="https://www.algolia.com/">Algolia</a> Search with our site update over the summer. Algolia is an excellent Search and Discovery platform, with features such as InstantSearch, Crawler, and Dynamic Synonym Suggestions, just to name a few.</p><figure><img alt="Algolia Logo" src="https://cdn-images-1.medium.com/max/1024/0*uENcTmHbjDIC06l4.png" /></figure><p>We dubbed our implementation Universal Search, allowing you to search subjects, courses, or camps. It&#39;s highly performant and is the exact search you&#39;ll see on STEMpump.org.</p><figure><img alt="Universal Search with pathways to Subjects, Courses, and Camps" src="https://cdn-images-1.medium.com/max/1024/1*B3fJ2AYijK3dFn8iOOAWxQ.png" /><figcaption>Universal Search — search for subjects, courses, camps, etc.</figcaption></figure><p>The Swift/SwiftUI implementation is a bit hit or miss, but it&#39;s flexible to build out our search and use the underlying functionality.</p><p>It can correct your mistakes while searching and even takes advantage of our underlying topics system. In addition, Universal Search works in real-time, with NLP (Natural Language Processing) and Dynamic Synonyms being able to help out.</p><p>It&#39;s a Search system that&#39;s almost human, knowing what you want, even if you don&#39;t know exactly what you&#39;re looking for.</p><h4>Building Guided Navigation</h4><p>Do you know what sucks? Interruptions in learning.</p><p>You want an uninterrupted process, allowing you to continue learning and doing nothing else. For example, in prior versions, to go to the next lesson, you needed to back out of your current lesson, click on the next one, and so on.</p><p>And honestly, it was a pain. Felt more like a directory than a course. So we&#39;ve provided new ways to traverse throughout a course in the latest version. For example, you can tap on the lesson list at the top right and choose lessons in the chapter or go to another chapter. Or, you can scroll down to the bottom of the page, where you&#39;ll have a card that allows you to continue.</p><figure><img alt="Two phones: one with a menu of lessons, the other with a card to move on to the next lesson" src="https://cdn-images-1.medium.com/max/1024/1*n0sqey63hva0aVEkCS_tPg.png" /><figcaption>Course Traversal Options</figcaption></figure><p>We&#39;ve experimented with varying types of navigation (and will most likely continue to do so) to find a natural solution — providing the option to self-traverse or go lesson after lesson.</p><p>This eliminates any interruption when it comes to learning, letting you learn however you&#39;d like.</p><p>There&#39;s so much more to talk about the development process of this app. It&#39;s the most extensive app I&#39;ve worked on, and so many different factors contributed to the state of where it is today. Like design, I hope to write more often about development in the future.</p><h3>Everything else</h3><p>Back to your regularly scheduled update log, with a few more awesome things coming with this app update.</p><h4>Camps</h4><p>STEMpump Camps (formerly STEMpump Online) makes a comeback! After 1.5 years of not teaching in real-time, we&#39;re ready to get back into it and better than ever before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V7Hqoev9FNb1s9UHwY9bPg.png" /></figure><p>We&#39;ve worked hard to refine every factor from STEMpump Online and make the experience fast, simple, and student-first.</p><p>You can register for upcoming camps, just like that. You can watch camps live and from the past. Everything has been rebuilt to provide an incredible experience.</p><h4>Quizzes and Projects</h4><p>Joining Lessons for the first time are Quizzes and Projects.</p><p>You can now take interactive quizzes with content directly tied to the course. In addition, there are multiple-choice and text-based questions, along with image and code-based questions.</p><figure><img alt="Two phones: one with a question from a quiz and the other with a Prime numbers project" src="https://cdn-images-1.medium.com/max/1024/1*yBetHFn1-etOJnU5dnXQQQ.png" /><figcaption>Quizzes and Projects!</figcaption></figure><blockquote><em>Fun Fact: Code in Quizzes are highlighted on-device, not on-server like Lessons and Projects.</em></blockquote><p>Projects are open exercises that allow you to apply course content directly. Follow the instructions and complete the project. There are a few hints if you get stuck. When you&#39;re done, check the solution to see if you&#39;re right!</p><h4>Updates to Courses</h4><p>Courses have been redesigned to provide more context than before. They are now arranged by Chapters for more accessible organization. Learn about Course status, content, and more extended summaries. In addition, new Learning Time functionality has been added to Courses, Camps, and Lessons.</p><figure><img alt="3 Phones: One of the course, the second of the extended information, and the third showing similar courses" src="https://cdn-images-1.medium.com/max/1024/1*htPMgmE5t7PYcNWuo1yRDA.png" /><figcaption>The all-new Course Design</figcaption></figure><p>Some courses have similar courses shown below them if you want to find anything similar.</p><h4>Preferences</h4><p>You can now change your app icon to all-new and redesigned versions of the STEMpump icon! In addition, you can delete all data stored on your device in a single click, or you can choose what to keep and what to delete.</p><h3>The Wishlist</h3><p>I decided to go back to that original post years ago and see what I wanted from the app at the time.</p><ul><li>Information about how long each course takes</li><li>Sharing the entire course with others</li><li>Offline Courses</li><li>Potential for using Adobe Fonts (?)</li><li>User System for personal growth</li><li>More interactivity</li><li>More Subjects</li><li>Less &quot;Non-Styling&quot;</li></ul><p>I think I solved all of these problems, in a way. The new app provides times on almost everything that one can read. You can hit the share button and share practically anything.</p><p>Offline Courses is interesting — I think with the current system, we might not be able to do that with whole courses, but maybe individualized lessons (and camp downloads 😉)</p><p><a href="https://community.adobe.com/t5/adobe-xd-discussions/using-adobe-font-in-mobile-app/m-p/10221710">Adobe Fonts is a no-no.</a> However, we do have a user system of sorts. There&#39;s a lot more interactivity and a few more subjects. We&#39;re using a lot of custom elements, too.</p><p>But I also remembered a draft post with a different wishlist:</p><ul><li>More web-specific features to the app create a cohesive STEMpump experience</li><li>Support iPadOS</li><li>Widgets?</li><li>Transition to using Markdown and smarter JSON objects</li><li>Look into creating a YouTube player</li></ul><p>And yeah, these all have been completed, except the Widgets part — which is in the works.</p><p><strong>3/18/22 UPDATE: Widgets just got done 😶</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jGSxnth2Hro3cKjehF8tw.png" /></figure><p>And it was a pain. But that’s a story for a different time.</p><p><strong>4/29/22 UPDATE: Burnt out! 😣</strong></p><p>I got so burnt out from working on the app that I uh… never finished or submitted it. (Creative burnout is real and I definitely struggle with it)</p><p>But this past week (with the fear of AP exams on the rise), I got everything else done, and more!</p><ul><li>Updated Announcements</li><li>V3 to V4 Transfer Tool for Favorites</li><li>Offline “Mode” (really just a complainer)</li><li>Remote Updating</li><li>Better refresh cycles</li><li>Lesson/Quiz/Project of the day</li><li>New design for Discover and Camps</li><li>In-App Events</li><li>Camp Countdown Timer</li></ul><p>Also, another story for another time! Back to your regularly scheduled essay.</p><h3>Conclusion</h3><p>This was a long post. If you read all ~20 minutes of it, thank you. It really means a lot.</p><p>The all-new STEMpump App is probably the biggest thing I&#39;ve done (besides STEMpump.org) and the most complicated app I&#39;ve built. Nevertheless, I&#39;m incredibly proud of it and excited to see where it goes.</p><p>It represents my journey and maturity in design and development, and I couldn&#39;t be happier with it. But who knows, a year from now, I&#39;ll probably be bashing this design 😜</p><p>If you like my work and want to continue to support it and STEMpump, please consider <a href="https://stempump.org/donate">donating</a>. Any amount makes a difference in our mission to provide free STEAM education.</p><p>You can download the app for yourself <a href="https://stempump.org/">here</a>. I would appreciate any feedback you can offer. Like always, if you want to chat or have questions, feel free to <a href="https://rtsh.space/">shoot me a message.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce17b03e71be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The making of the STEMpump App]]></title>
            <link>https://riteshkanchi.medium.com/the-making-of-the-stempump-app-da452a95fbd0?source=rss-5a56cf738ae6------2</link>
            <guid isPermaLink="false">https://medium.com/p/da452a95fbd0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[stem]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Ritesh Kanchi]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 18:23:50 GMT</pubDate>
            <atom:updated>2020-11-26T00:12:55.020Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Making of the STEMpump App V1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJ-g61U9JjS3vAtchUMzVQ.png" /><figcaption>The STEMpump App</figcaption></figure><p><strong>What is STEMpump?</strong></p><p>STEMpump is a student-led initiative that teaches students the best of STEM technologies. I created this program as a way to give back to my community by sharing our passion for STEM. We teach three-hour bootcamps at our school teaching different STEM skills. Since its inception in September 2019, we have taught a variety of free courses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kLTGJ5BGZuEhnczOZw6lQ.png" /><figcaption>Courses we have taught at STEMpump (With more to come!)</figcaption></figure><p>Our program gained attention not only in our district, but all across our region. Since September, we have taught over 150 students, across all grades, coming from 21 schools within 6 districts.</p><blockquote>“With a methodology to help students become science and technology leaders, as well as well-rounded contributors to society, it’s no wonder why a program like FIRST would inspire FMHS students to not only contribute to society but share their knowledge of science and technology with others. And, for free.”</blockquote><blockquote><strong>— Lewisville Independent School District</strong></blockquote><p>Teaching courses to students was nothing new of course, tons of other students across our region were doing it. What makes us different was that following every one of our bootcamps, we post our online curriculum, so anyone could follow along. Every line of code to every specific instruction, all is available. We made sure everything we taught and then some was available in our <a href="https://stempump.com/resources">online resources page</a>.</p><p>STEMpump’s online resources catalog has been evolving over the past few months. What once was a simple static page, is now a dynamic system, working with a CMS(Content Management System) to control all the data. In developing the system that both the site and app operate on, I have learned a lot overall and am thankful for this opportunity.</p><p><strong>When did the app come into the picture?</strong></p><p>From the beginning, I always knew creating an app for STEMpump was the next big picture item I wanted to do. But first, I had to make sure our courses had to be completely dynamic with data that could interact with other types of uses that we would eventually create. I toyed around with the idea of making an app, and then in December 2019, I finally did so.</p><p><strong>SwiftUI</strong></p><p>Back in June, Apple unveiled a new framework they had been working on, SwiftUI. A competitor to React Native, SwiftUI was designed to make app development and the visual design aspect of the experience easier for the developer.</p><blockquote>SwiftUI is an innovative, exceptionally simple way to build user interfaces across all Apple platforms with the power of Swift. Build user interfaces for any Apple device using just one set of tools and APIs.</blockquote><blockquote>— Apple</blockquote><p>During the Summer, I played with it, creating a few basic apps to test the capabilities. I knew that it was a powerful framework that was in the future of app development no doubt. It could make development for both iOS and iPadOS so much easier without the need of constraints and storyboards. I left it for a while, but over the winter got back into it.</p><p>I have always been interested in development for Apple’s ecosystem, and that’s a bit of what lead me towards this over React Native’s cross-platform system.</p><p>Working with SwiftUI for this long, I definitely think it is the future for Apple’s ecosystem. Everything is very easy to use (but very buggy in some instances). A novice could get a basic interface done very quickly. The simplicity of States and Binding make it very easy to connect data, control taps and drags, as well as animate different views. While I still have a few complaints about the struggle it can be to do the simplest of things, I believe that this is a framework that has unlimited potential.</p><p><strong>STEMpump App: Builds 1–10</strong></p><p>So during the time in December, in a week, I created the first stable build of the STEMpump app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xh9aK90NqntieUIxSUeYw.png" /><figcaption>A few screens of the stable build of the app.</figcaption></figure><p>I’m gonna be honest. There are a lot of issues with this app.</p><ul><li>Way too simple, nothing that stands out. The design is very “basic”-esque with very limited styling.</li><li>Semi-Dynamic Data. The Courses could be added/removed through full updates of the app.</li><li>Zero design work was put into this. This resulted in a poor user experience.</li><li>One word. WebViews. There were WebViews everywhere. I wasn’t able to get the JSON data on our server interacting with the app dynamically, so I created arrays that pulled the website pages with modified styling. It was a very cheap way to do it.</li></ul><p>Those were just a few problems I could list off the top of my head, but there were definitely more. School kicked in, and I didn’t spend that much time on the app for a while.</p><p><strong>STEMpump App: Builds 11–22</strong></p><p>Spring Break. Yay! This was the free time I’ve been waiting for. I was browsing online, and saw a video about some cool things I could do in SwiftUI. That kinda triggered the idea of continuing the development this app. I wasn’t going to give up that easy. I scrapped the original app I made in January and restarted the entire process.</p><p>The entire app was made in about 1–1.5 week(s). I spent a good portion of the week working on the design of the app, creating mockups in Adobe XD and Sketch, along with prototyping interactions. I wanted a design that felt modern and bubbly, but still approachable as user-friendly. I experimented with lots of interfaces, keeping the limitations of SwiftUI in mind at all times. Finally, I came up with a design a bit reminiscent of the original app I created, but still different. I went through tons of iterations before finally settling on one I believed checked all my boxes for the time being.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1h0hoF7Et6A4pGg5sE2_A.png" /><figcaption>One of my original artframes</figcaption></figure><p>Throughout the design phase, I wanted to keep as much of the STEMpump brand as I could. I wanted the interface to be easy to use, so anyone could pick it up and learn something new. The organization of how the courses and sections were laid out was also something I focused on. I decided to use two horizontal scrollers on the home page: One for the sections, and one for featured courses. Then, within each section block, there would be a vertical scroller with each of the</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0USKBGPTa3O6oy3RnqBoVA.png" /><figcaption>STEMpump App artframes from XD</figcaption></figure><p>Development was the harder part. I had to make sure that everything would connect to the flow of the data from the STEMpump web server. We currently had each course’s lessons in individual JSON files, which I realized was a big mistake. This would stunt how I could make Swift interpret the data. So, I ended up taking those JSON files and merging them into a single JSON file (which was the best move.)</p><p>As mentioned above, I had to make sure that the data flow was perfect. The website needed to have the exact information the app had. This meant that when I updated the course on the site, the app would auto update. In order to do this, I had to redesign how the JSON flows on our site. What once had tons of static data being added was now replaced by a super simple system. In layman’s terms: When the JSON updated, everything updated as well. Just like that. In total, the STEMpump app and website use two JSON structures: one for all of the courses, and another for all the lessons per course. This lowers the amount of files to pull from and also simplifies the data pathway.</p><p>The final data flow looks something like below in the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdUJxSR4ym6yBoHIuvkVXg.png" /><figcaption>Data flow of website and app interactions</figcaption></figure><p>Without redesigning how our website interpreted the JSON data, we could never have 1:1 updating between the app and website. One of the big parts that I am very proud of is that I can go into the Course JSON Data, and it auto updates everywhere across the board.</p><p>Another goal I had was to make the app as small as I could. Using <a href="https://github.com/SDWebImage/SDWebImageSwiftUI">SDWebImage</a>, I could make sure that images could be stored on our server, once again making everything simplified. I store a few essential images in the app, but everything else could be held off, on our server.</p><p>In the original app, I used WKWebViews that displayed a webpage on our server. In this new app, I wanted everything to be as dynamic and easy to control as possible. Using the WKWebView, I was able to reconfigure it so rather than load a webpage, it could interpret HTML, CSS, and Javascript. Right there in the app. I originally wanted to be able to display text and images natively, but there isn’t (at least not right now) a good way to display Strings and Images intertwined in SwiftUI, without any complex work to figure it out. So, I took web page, and cleaned it out, making it so only a few variables needed to be plugged in for the page to show. This improved load times as well, since most of the data was already was in Strings in the app.</p><p>The organization of the courses is something I really wanted to get done well. We organize our courses into four subjects/sections:</p><ul><li>Robotics</li><li>Programming</li><li>Creation</li><li>Game Design</li></ul><p>Rather than show everything we have available, I thought it was a better idea to sort the courses based on the subject they most aligned with. Each subject has a JSON file for it, that contains all the courses that align under itself. From there, it follows the same path as clicking from the featured page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sdvkes5fzvS69iDIA0F3MA.png" /><figcaption>Opening a course</figcaption></figure><p><strong>Simplified</strong></p><p>Here is a simplified list of everything that I used during the creation of this app.</p><ul><li>Adobe XD/Sketch to layout a design (Extremely important, helps with SwiftUI development)</li><li>JSON Structures to connect website and app to same data</li><li>API configuration in Swift to interpret the JSON data</li><li>WKWebViews to interpret HTML, CSS, and JS</li><li>SDWebImage to receive images from URLs</li><li>States and Bindings to control Sheets</li><li>RGB Colors controlled by JSON data to determine colors for each</li></ul><p>All in all, this app wasn’t that complicated to create, but has a very strong potential to get complex and better.</p><p><strong>The future</strong></p><p>There’s so much more I want to add and work on towards this app. It isn’t perfect, which allows me to spend more time on getting it to that position. Some of the ideas I have for future updates include:</p><ul><li>Information about how long each course takes</li><li>Sharing the entire course with others</li><li>Offline Courses</li><li>Potential for using Adobe Fonts (?)</li><li>User System for personal growth</li><li>More interactivity</li><li>More Subjects</li><li>Less “Non-Styling”</li><li>And so much more.</li></ul><p>Along with all those, I am interested on making a counter-part for Android. I have learned a lot about Swift through this experience, and I want to learn to use Flutter/Dart and React Native. Using one codebase is a lot simpler than trying to juggle two at a time.</p><p><strong>Thanks for reading!</strong></p><p>This was my first Medium post, and I plan on doing a lot more of them in the future. If you have any questions or comments, feel free to contact me <a href="https://ritesh.digital/contact.php">here</a>. If you want to check out STEMpump, check it out <a href="https://stempump.com/">here</a>.</p><p>You can download the app for yourself <a href="https://stempump.com/app">here</a>. Thanks again for reading my post detailing this app’s journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da452a95fbd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>