<?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 Chacko on Medium]]></title>
        <description><![CDATA[Stories by Chacko on Medium]]></description>
        <link>https://medium.com/@sajucrajan?source=rss-4b35dd4c6eef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Sre5HbLjQKQQkDBiKtz7Ng.png</url>
            <title>Stories by Chacko on Medium</title>
            <link>https://medium.com/@sajucrajan?source=rss-4b35dd4c6eef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:06:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sajucrajan/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 AI Gets It Wrong, You Pay; For Everything Else, There Is Insurance]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/when-ai-gets-it-wrong-you-pay-for-everything-else-there-is-insurance-0de81a59dd97?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/2600/1*MhX65pU9xb6CfhpRAHT-pw.jpeg" width="2752"></a></p><p class="medium-feed-snippet">As AI gets primetime, isn&#x2019;t it time the AI models and model owners pay for the mistakes the model makes?</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/when-ai-gets-it-wrong-you-pay-for-everything-else-there-is-insurance-0de81a59dd97?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/when-ai-gets-it-wrong-you-pay-for-everything-else-there-is-insurance-0de81a59dd97?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/0de81a59dd97</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 02:27:02 GMT</pubDate>
            <atom:updated>2026-09-21T02:27:02.295Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What Is a “Hello, World” Program? The Six Steps It Really Tests]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/what-is-a-hello-world-program-the-six-steps-it-really-tests-de409af644da?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/2600/1*u9WUBrEjuX1P7250KvrNlw.jpeg" width="2752"></a></p><p class="medium-feed-snippet">&#x201C;Hello, World&#x201D;&#x200A;&#x2014;&#x200A;Almost every programmer would have typed this at least once but understood by only few of them</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/what-is-a-hello-world-program-the-six-steps-it-really-tests-de409af644da?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/what-is-a-hello-world-program-the-six-steps-it-really-tests-de409af644da?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/de409af644da</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 22:58:44 GMT</pubDate>
            <atom:updated>2026-08-27T22:58:44.272Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Last Human in the AI Loop]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/the-last-human-in-the-ai-loop-094aa929a063?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/2600/1*cMYOrGTpRUmRdMIpJG4q_g.png" width="2752"></a></p><p class="medium-feed-snippet">What&#x2019;s left for the developer, the QA, the architect, and the manager when the AI machines do the technical work</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/the-last-human-in-the-ai-loop-094aa929a063?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/the-last-human-in-the-ai-loop-094aa929a063?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/094aa929a063</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 03:14:37 GMT</pubDate>
            <atom:updated>2026-08-17T03:14:37.460Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Month of AI Credits, Gone in Two Days]]></title>
            <link>https://sajucrajan.medium.com/a-month-of-ai-credits-gone-in-two-days-7aaf120861e7?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aaf120861e7</guid>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[aritificial-intelligence]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-07-13T11:01:01.339Z</atom:updated>
            <content:encoded><![CDATA[<h4>ON THE COST OF AI TOOLS</h4><h4>What GitHub Copilot’s new per token billing taught me about my team, my habits, and a question I still can’t answer</h4><blockquote><a href="https://medium.com/it-chronicles/the-real-cost-of-an-ai-coding-assistant-40330af8b0c8">→ The Real Cost of an AI Coding Assistant</a></blockquote><p>One of our managers burned through an entire month of AI credits in two days.</p><p>He wasn’t being careless. He got absorbed in a side project, pointed the assistant at it, and let it run. Nothing about how he worked had changed. What changed was how GitHub charges for it.</p><figure><img alt="A month of AI credits, gone in two days (Illustration generated with Google Gemini)" src="https://cdn-images-1.medium.com/max/1024/1*tY869BITE1gIprRcoKELaw.png" /><figcaption>A month of AI credits, gone in two days (Illustration generated with Google Gemini)</figcaption></figure><blockquote>On June 1st, Copilot stopped charging per prompt and started charging per token. That one sentence turned out to be the whole story - and it reached me three separate times, as a developer, as an architect, and as the manager of the team living with the limit.</blockquote><figure><img alt="He wasn’t being careless (Illustration generated with Google Gemini)" src="https://cdn-images-1.medium.com/max/1024/1*qU0JteBvpXB4qjR-ae3JHw.png" /><figcaption>He wasn’t being careless (Illustration generated with Google Gemini)</figcaption></figure><blockquote>The part that caught me had nothing to do with money.</blockquote><figure><img alt="I asked an AI to reverse a string (Illustration generated with Google Gemini)" src="https://cdn-images-1.medium.com/max/1024/1*u34aGRC5rAuMC8npsg1ouA.png" /><figcaption>I asked an AI to reverse a string (Illustration generated with Google Gemini)</figcaption></figure><blockquote>And the part that still bothers me had nothing to do with me.</blockquote><figure><img alt="Can the human still tell? (Illustration generated with Google Gemini)" src="https://cdn-images-1.medium.com/max/1024/1*ZG-TPUvH3E_FDtOqtuZxkw.png" /><figcaption>Can the human still tell? (Illustration generated with Google Gemini)</figcaption></figure><blockquote>I wrote the whole thing up - what actually changed in the billing, what it cost my team, what my team did about it that I’m not proud of, and the question I couldn’t answer at the end.</blockquote><figure><img alt="Read the full story (Illustration generated with Google Gemini)" src="https://cdn-images-1.medium.com/max/1024/1*KT_nsVo1hl7mXnpT60Jo4g.png" /><figcaption>Read the full story (Illustration generated with Google Gemini)</figcaption></figure><blockquote><a href="https://medium.com/it-chronicles/the-real-cost-of-an-ai-coding-assistant-40330af8b0c8">→ The Real Cost of an AI Coding Assistant</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aaf120861e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real Cost of an AI Coding Assistant]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/the-real-cost-of-an-ai-coding-assistant-40330af8b0c8?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/1376/1*5AteAZEaluNhVl8ypEDQbA.png" width="1376"></a></p><p class="medium-feed-snippet">GitHub Copilot went from charging per prompt to per token, and the bill turned out to be about me</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/the-real-cost-of-an-ai-coding-assistant-40330af8b0c8?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/the-real-cost-of-an-ai-coding-assistant-40330af8b0c8?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/40330af8b0c8</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[github-copilot]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Sat, 11 Jul 2026 13:53:49 GMT</pubDate>
            <atom:updated>2026-07-11T13:53:49.797Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Built a Tool to fight AI Assisted Remote Interviews]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-iii-91d11bee75a6?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/2600/1*DlPaWlr7e-nBWztwqDV9xA.png" width="2752"></a></p><p class="medium-feed-snippet">Dayside is a small, open-source, local-only scanner that puts the interview back in daylight</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-iii-91d11bee75a6?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-iii-91d11bee75a6?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/91d11bee75a6</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Fri, 19 Jun 2026 23:20:59 GMT</pubDate>
            <atom:updated>2026-08-29T13:09:10.673Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What AI Interview Cheating Actually Costs]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-ii-887c37ee159f?source=rss-4b35dd4c6eef------2"><img src="https://cdn-images-1.medium.com/max/2600/1*6uIhuXMmfjyQ5OjTkbHc3A.png" width="2752"></a></p><p class="medium-feed-snippet">Nobody in the chain that built this is going to stop and your defenses don&#x2019;t work anyway</p><p class="medium-feed-link"><a href="https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-ii-887c37ee159f?source=rss-4b35dd4c6eef------2">Continue reading on IT Chronicles »</a></p></div>]]></description>
            <link>https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-act-ii-887c37ee159f?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/887c37ee159f</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ethical-ai]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 22:09:39 GMT</pubDate>
            <atom:updated>2026-08-14T10:55:27.821Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Remote Interviews Fail, Trust Fails and Projects Fail - Act I]]></title>
            <link>https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-e46094c43c0d?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e46094c43c0d</guid>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 23:21:38 GMT</pubDate>
            <atom:updated>2026-06-05T02:41:05.243Z</atom:updated>
            <content:encoded><![CDATA[<h4>HIRING IN THE AI ERA</h4><h4>How invisible AI assistants quietly broke the remote technical interview</h4><figure><img alt="A year ago I trusted this format. I don’t anymore. (Illustration generated with Google Gemini.)" src="https://cdn-images-1.medium.com/max/1024/1*WtqIdidp9VRVjLOkvVSd8Q.png" /><figcaption>A year ago I trusted this format. I don’t anymore. (Illustration generated with Google Gemini.)</figcaption></figure><p>I run technical interviews. Over the past year, invisible AI assistants have quietly broken the format. This is what I’ve seen, what it costs, how it impacts an interviewer, a team, a project, or an organization and what I built in response.</p><h3>A year ago I trusted this format. I don’t anymore.</h3><p>I schedule and take technical interviews for my company. My colleagues, team members and I have been doing it for years, across several data platforms and several technical roles, and we thought we understood the shape of the problem. Now we can see certain patterns and understand what kind of candidate is interviewing with us.</p><p>If the candidate’s answers are too polished or too fast or even too correct on problems that should have taken some time, the interviewers will feel something is wrong or that the candidate is unethical. We can’t prove anything. We can’t see anything. But we can feel it during the interview process.</p><p>And then, a few times, we hired the person anyway because the interview came back positive, because the interview panel was confident in the candidate and a few weeks in, the new hire had no clue about the work and simply could not match the interview performance. It would be something basic like checking in the code to GitLab or GitHub.</p><p>It was not an onboarding issue, it was not a stretch goal, but it was a fundamental mismatch between what the interview suggested the person could do and what they were actually able to do once they were assigned work and there was nobody feeding them answers.</p><p>The cost of that mismatch is not theoretical. The project lost weeks of delivery. The project missed the timelines. The process cost the organization time and money. We had to start the hiring process all over, which meant another interview process, multiple rounds of interview hours, and extra hours during weekends the team would need to stretch and cover efforts of the unfilled seat.</p><p>The downstream teams or consumers don’t need to know or care that we’d made a bad hire in good faith. The project slipped either way impacting other teams also dependent on the same delivery.</p><p>Once it started happening multiple times in different teams in our group, it stopped feeling like bad luck and started feeling like started feeling like we weren’t able to weed out the imposters and the interview format itself was broken.</p><p>When a panel of interviewers, where each interview has at least a decade of experience, can’t tell whether the answers are coming from the candidate on the screen, the interview shifts from measuring whether the person can do the job to measuring whether the person is actually doing something unethical and getting help in someway to answer questions. The whole purpose flips. You sit down to evaluate a candidate and instead lose forty-five minutes running an integrity check.</p><p>That flip is the actual story. The unethical tools are what flipped the whole interview process.</p><p>This article is about my thoughts on that inversion and what caused it, why nothing in our existing interview process can catch it, and the small open-source tool(s) I built that intends to help the interview to get back the thing an interview is supposed to be.</p><p>I want to be honest upfront since this isn’t a solved problem. The tools I’m publishing are a first line, not a last line. But something is better than nothing as nothing is roughly what most interviewers have today in my knowledge, other than the ultimate in person interview.</p><figure><img alt="Each fix held until the next wave made it look small. (Illustration generated with Google Gemini.)" src="https://cdn-images-1.medium.com/max/1024/1*OPzVZtQMTfxUacwyH-s47w.png" /><figcaption>Each fix held until the next wave made it look small. (Illustration generated with Google Gemini.)</figcaption></figure><h3>Part I - The arms race so far</h3><p>It’s worth mentioning how we got here, because the AI didn’t appear out of the blue. My team watched the unethical interviews creep in steps over the last few years. Each unethical style started looking like the last problem until the next one made the previous issue look small.</p><p>The first version we ran into was <strong>person-swapping</strong>. The actual candidate will show up in the initial screening round that verifies the ID and the actual person is same and then a different person, will show up for the remote technical round. A complete swap, only during the remote interview.</p><p>The fix was easy, we checked ID against the camera, asked the candidate to show their face clearly, sometimes asked a quick question like the birthdate or full name with spelling for which only the actual person would be able to answer. Annoying but tractable and effective.</p><p>Then we caught a few candidates who had other people in the room help answer the question. The candidate would try to <strong>lip sync</strong> or just move the lips and assume the interviewer would think the network had an issue, or accept it’s the way the candidate speaks.</p><p>The defense was a room scan - politely - asking the candidate to unblur the background and pick up the laptop and pan around their room at the start of the interview to confirm no one else is there and face the camera towards the door to ensure no one enters after the initial room scan. This may have bothered some candidates, but the interviewers also need to feel sure and not feel fooled by the over-smart candidates.</p><p>The next unethical practice we found, and this one took us longer to figure out, was when a candidate, alone in a separate room, was still able to get answers fed to them by someone else. The candidate’s machine was being controlled remotely. One person or sometimes a group of people in different locations, sometimes a group of friends, sometimes a paid service, would listen, watch, and control the interview through a remote-desktop connection and provide the answers for the candidate.</p><p>The candidate sat there reading and acting as if they were typing the answers that was showing up their screen and explaining it as if they had come up with it. This was just one incident, and we discovered it by accident when the person shared his screen and we saw a Zoom window with three names we didn’t recognize, while the actual interview was supposed to be on a Teams call. He dropped off as soon as we asked him about the other call. We did not have a defense or fix for this but to check for any processes or icons of applications that we did not recognize or knew to be remote login or control applications.</p><p>Then the AI assistants arrived, and they made all of those previous defenses look unimpressive. AI did not need a person off-camera. It did not need a remote operator. AI did not need a second device. The AI application or software ran on the candidate’s own machine, in a process or window that screen-share cannot see, listening to the interview audio and feeding answers in real time. There is no second person to find out. There is no remote connection. The only attacker in the room is software, and the software is invisible to teams calls by design.</p><p>Each previous form of unethical interview was solved by a procedural fix that felt slightly intrusive but was at least possible. The AI usage for unethical interviewing is different and something new even for the interviewers. Initially, the candidate had to do something for AI to get an input before it could provide the answer. So we could feel it when the candidate took some time and added filler words to fill the time between the question and the time AI took to generate the answers. So the candidate would fumble around for a bit and suddenly they have the perfect answer. But that also changed.</p><p>In the latest version of the AI, it doesn’t take much time between the AI getting the information and providing an answer. Our existing defenses don’t catch all this. We’ve moved from problems with some solutions to a problem whose solution requires some new tool or process or a fundamentally different interview format.</p><p>The fundamentally different format was an in-person interview at our office or in an office that is a safe space, like a vendor office, on a non-personal device provided by the vendor partner. This article is about my attempt to build a tool that can clear a genuine interviewee and also help the interviewers focus on the interview rather than trying to ensure no unethical practices are being used.</p><figure><img alt="No person to detect. No remote connection. No second device. (Illustration generated with Google Gemini.)" src="https://cdn-images-1.medium.com/max/1024/1*T-KCX3WqFcvMUMBBsIyq6A.png" /><figcaption>No person to detect. No remote connection. No second device. (Illustration generated with Google Gemini.)</figcaption></figure><h3>Part II - The shape of the AI problem</h3><p>The category of software that broke the remote interview format is moving fast. The new programs that use AI for unethical reasons do the following.</p><ul><li>Browser-based assistants and plugins can listen to the interview audio, transcribe questions in real time, and display suggested answers in the same browser window based on the last question. The candidate do not install anything in their machines. The service is marketed “no download required” helper or assistant for interviews.</li><li>Desktop overlay software with adjustable opacity (60% to 80%), set to stay on top of other windows. The candidate can see the interview panel meeting along with any questions the panel shares or LeetCode problems the interviewer wants answered, then respond without switching windows or opening new tabs during the interview. This is only possible if the candidates do not do any screen share.</li><li>Newer desktop overlay applications are not visible in a screenshot or screen grab. This is the craziest version of the unethical AI software, and the one with the biggest impact on the interview process. <br>All operating systems have APIs that let a window flag itself as “please do not include during screenshots”. Those APIs are built for legitimate reasons, so privacy is maintained and no unwanted information is leaked into a shared video call. Invisible AI assistants use these operating system features to unethically render answers in a floating window that the candidate can see and refer to while the interviewer watching the same screen over Teams or Zoom sees nothing else.</li><li>Second-device tools are impossible to find and avoid, phones propped up out of camera view, a second screen connected to another laptop, or even a tablet mirrored to a hidden display. I am not categorizing second-device tools as an AI only problem.</li></ul><p>The application providers or websites providing such assistance are not hiding. They list multiple features that can avoid detection. They may have some sort of funding, growth teams, and testimonials (not sure if they are fake testimonials or not). These are not shadowy applications or tools that are hidden. This is available and open to all who are willing to pay to get an advantage in their upcoming interviews.</p><p>Rather than calling out specific websites or applications (and to avoid any legal repercussions), I’ll call the pattern GhostPrompt which is a comprehensive mix of capabilities that, together, characterize this category.</p><p>Now, please understand there is no tool called GhostPrompt as of today so don’t go searching for it. There is other software you can buy today from a simple Google search, as their SEO ranks the highest, and most of the well-known products combine three or four of these capabilities into a single service.</p><p>Tools that belong to the GhostPrompt category run on the candidate’s laptops or desktops. In such circumstances we can always see the candidate will not have a headset or microphone and takes the interview on the laptop or device speaker and microphone.</p><p>The GhostPrompt application listens to the interview audio through the system speaker and microphone. When the interviewer asks a question the application can transcribe it and send it to a large language model, and display the answer in a floating overlay window the candidate can read while the interview continues. The window is set to exclude itself from screen capture, so the interviewer staring at the same screen over Zoom via screen share sees nothing.</p><p>The candidate can read or refer to the answer, say it in their own words after a little bit. The screen share only sees the candidate’s desktop or browsers. There is no clue left behind of the interviewer to suspect something else is happening.</p><p>This is happening in the onsite interviews, in the United States, and also in the offshore interviews from India. The user base adopting the unethical interview hacks is growing large.</p><p>This is where ACT I ends. If you have somehow managed to read so far, you have understood the issue, what these tools actually do, how we got here and why it is not going to go away any time soon.</p><p>The <strong>“</strong><a href="https://medium.com/p/887c37ee159f"><strong>Remote Interviews Fail, Trust Fails and Projects Fail — Act II</strong></a><strong>”</strong> is going to be about how this impacts the real work. It covers the wasted recruiter and interview panel hours, the wrong hires that break projects, and the collapse of the remote interview process. I’ll also try to explain why the screen sharing or video checks no longer work. If a group of people are openly building tools to break the interview process, why is nobody doing anything to stop them? I guess everyone is thinking somebody is going to take care of this.</p><p><a href="https://medium.com/p/887c37ee159f">Act II</a> is about the IMPACT and Act III is about ACTION.</p><figure><img alt="Now What? (Illustration generated with Google Gemini.)" src="https://cdn-images-1.medium.com/max/1024/1*CF9lqSidrgqaAd4Eto6FNw.png" /><figcaption>Now What? (Illustration generated with Google Gemini.)</figcaption></figure><blockquote>Support writers. All our non-profit’s offerings <a href="https://forms.gardenofneuro.org/nx/portal/neonevents/events?path=%2Fportal%2Fevents">here</a>.</blockquote><blockquote><a href="https://medium.com/it-chronicles/newsletter">Click here to subscribe to the IT Chronicles newsletter.</a></blockquote><blockquote><a href="https://forms.gardenofneuro.org/nx/portal/neonevents/events?path=%2Fportal%2Fevents">Click for Wordsmith, Mystery Writing, Write Like Stephen King, more</a></blockquote><figure><a href="https://medium.com/it-chronicles"><img alt="Computer circuit pathways" src="https://cdn-images-1.medium.com/max/1024/1*bX_AIumALEvtJr-mZIBeMw.png" /></a><figcaption>By the EIC <a href="https://medium.com/u/cc0821aee9c1">Susan Brearley</a> with Ideogram</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e46094c43c0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/it-chronicles/remote-interviews-fail-trust-fails-projects-fail-e46094c43c0d">Remote Interviews Fail, Trust Fails and Projects Fail - Act I</a> was originally published in <a href="https://medium.com/it-chronicles">IT Chronicles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jetpack Compose — Android — Navigation Component — Beginner Steps — Part 2 (Practice)]]></title>
            <link>https://sajucrajan.medium.com/jetpack-compose-android-navigation-component-beginner-steps-part-2-practice-5122b3dbfe73?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/5122b3dbfe73</guid>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[andriod-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[andriod]]></category>
            <category><![CDATA[navigation-component]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Sat, 07 Jan 2023 07:38:53 GMT</pubDate>
            <atom:updated>2023-01-07T11:59:38.415Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jetpack Compose — Navigation Component Android — Beginner Steps — Part 2 (Practice)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_kS7MUudD-OdIX0I5DHv2g.png" /></figure><p>This is Part 2 of the Jetpack Compose — Android — Navigation Component — Beginner Steps. The Part 1 of this article introduced us to navigation and and the 3 pieces of Navigation component in Jetpack compose.</p><p>The navigation component requires 3 pieces in its implementation within an android application:</p><ul><li><strong>Navigation Controller — NavController</strong></li><li><strong>Navigation Host — NavHost</strong></li><li><strong>Navigation Routes/Destinations</strong></li></ul><p>Without further adieu lets&#39; start with the steps for implementing Navigation in Jetpack compose.</p><blockquote>Assumption: I’m assuming that you have Android Studio and Java 11 installed in your windows or apple personals machines. I’m also assuming that you have the knowledge of creating a new Android project using the Android Studio and selecting the ‘Empty Compose Activity’.</blockquote><h4>Table of Contents</h4><p>∘ <a href="#6ec4">Steps to implementing Navigation in Jetpack compose:</a><br> ∘ <a href="#5acd">1. Create an Android Project — Navigation Guide</a><br> ∘ <a href="#4cac">2. Cleaning up the Project</a><br> ∘ <a href="#75df">3. Adding the Navigation library dependency to the project</a><br> ∘ <a href="#8f5c">4. Thinking &amp; Designing the application route flow</a><br> ∘ <a href="#1d21">5. Create a navigation routes map (sealed class)</a><br> ∘ <a href="#e0cb">6. Create a Navigation Controller</a><br>· <a href="#2ce2">Creating the Screens (Destinations)</a><br> ∘ <a href="#8194">7. Create Entry Screen</a><br> ∘ <a href="#969c">8. Create the Login Screen</a><br> ∘ <a href="#fc15">9. Create the Register Screen</a><br> ∘ <a href="#0cad">10. Create the Welcome Screen</a><br> ∘ <a href="#1503">11. Create the Logout Screen</a><br> ∘ <a href="#7759">All UI screens preview</a><br> ∘ <a href="#0945">12. Create and Invoke the Navigation Host </a><br> ∘ <a href="#f1a5">13. Adding Navigation instructions to button clicks</a><br> ∘ <a href="#7842">14. Extract &amp; Pass username from navigation back stage entry </a><br> ∘ <a href="#a3a2">15. Wow! We are finally done. Testing Time</a><br>· <a href="#165f">Conclusion</a></p><h4>Steps to implementing Navigation in Jetpack compose:</h4><h4>1. Create an Android Project — <em>Navigation Guide</em></h4><p>Create a new Android application using the ‘<strong>Empty Compose Activity</strong>’ with project name ‘<strong>Navigation Guide</strong>’. If you need any help in setting up Android Studio and create you first application, use the guid below.</p><p><a href="https://medium.com/@sajucrajan/starting-with-jetpack-compose-setting-up-android-studio-beginner-steps-dc908a50484c">Starting with Jetpack compose — Setting up Android Studio — Beginner Steps</a></p><h4>2. Cleaning up the Project</h4><p>The ‘Empty Compose Activity’ Android project gets created with some broiler plate code that displays ‘Hello Android’. We will cleanup the Greeting function as well as the Preview composable and then we will add a new empty composable named MainScreen(). After the cleanup the code in <strong>MainActivity.kt</strong> will look like this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4125ba0eeda89ace4f96ef4d548b58b/href">https://medium.com/media/a4125ba0eeda89ace4f96ef4d548b58b/href</a></iframe><h4>3. Adding the Navigation library dependency to the project</h4><p>For using the navigation component, we have to add additional project dependency in the project build.gradle file. This allows the Android Studio project to download the code packages required to support developing the navigation component in our project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVHvmDdNIbrrzck6jsMiAg.png" /></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/43b35bb11de3ce8909810294f959b41d/href">https://medium.com/media/43b35bb11de3ce8909810294f959b41d/href</a></iframe><p>After adding the dependency in the build.gradle, click on the ‘<strong>Sync Now’</strong> button on the top right of the android studio editor. The ‘<strong>Sync Now’ </strong>process starts a gradle task that looks through all of the project dependencies listed in your build.gradle file and tries to download the specified version from the configured repositories. The default configuered repositories are google() and mavenCentral().</p><p>Read more about Gradle + Groovy Dependency Management using below link:</p><p><a href="https://docs.gradle.org/current/userguide/groovy_plugin.html#sec:groovy_dependency_management">The Groovy Plugin</a></p><h4>4. Thinking &amp; Designing the application route flow</h4><p>So, before we start coding for navigation or creating screen, we have to think through our application route flow. I have created a wireframe map that can help understand the flow and how the navigation routes and destination is expected to function.</p><p>From the wireframe flow, we can see that there are 5 different destinations that needs routes for navigation.</p><ul><li>Entry Screen</li><li>Login</li><li>Register</li><li>Welcome (after Login/Register)</li><li>Logout</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_kS7MUudD-OdIX0I5DHv2g.png" /></figure><p>This is a very simple and straight forward navigation map that we will create. The <strong>Entry Screen</strong> have two destinations, the <strong>Login screen</strong> and <strong>Registration screen</strong> based on which button or link was clicked by the user. From both the Login and Register screen the user will be navigating to the <strong>Welcome screen</strong> after the user clicks the ‘<strong>Continue</strong>’ or ‘<strong>Register</strong>’ button. The welcome screen allows the user to click the ‘<strong>Log Out</strong>’ button to navigate to the Logout screen and then navigate back to the <strong>Login screen </strong>by clicking the ‘<strong>Log In</strong>’ button.</p><h4>5. Create a navigation routes map (sealed class)</h4><p>We now know our navigation destination screens from the step above. To starting implementing the navigation in our project we will create the routes for our five destinations. For defining the routes, we will use a sealed class which is very similar to enum class in Java. Read more about <a href="https://kotlinlang.org/docs/sealed-classes.html"><strong>sealed class here</strong></a></p><p><strong>Create a new </strong><strong>package named </strong><strong>navigation <br></strong>Right click the navigationguidepackage -&gt; New -&gt; Package<br>Name the package <strong>navigation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*N2ELkQ3LDOQLBQaRYJ9JOA.png" /></figure><p>Create a class named Navigation Routes a<br>Right click the navigation packages -&gt; New -&gt; Kotlin Class/File<br>Select Sealed Class and name the class NavigationGuides</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*Rw7bHQW3Mil4KdVTC68-1g.png" /></figure><p>Once the Sealed Class is created, we will create the destination routes as follows:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ea69adbfb2891613958f5574307759e/href">https://medium.com/media/2ea69adbfb2891613958f5574307759e/href</a></iframe><h4>6. Create a Navigation Controller</h4><p>The <a href="https://developer.android.com/reference/androidx/navigation/NavController">NavController</a> is the central API for the Navigation component. It is stateful and keeps track of the back stack of composables that make up the screens in your app and the state of each screen.</p><p>You can create a NavController by using the <a href="https://developer.android.com/reference/kotlin/androidx/navigation/compose/package-summary#rememberNavController(kotlin.Array)">rememberNavController()</a> method in our MainActivity.kt:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9766a9563f9607e6e3e83f981226c489/href">https://medium.com/media/9766a9563f9607e6e3e83f981226c489/href</a></iframe><h3>Creating the Screens (Destinations)</h3><p>There are five destinations / screens that we need create before it can be used for navigation. We will create the screens in a new package namesd screens inside the package com.example.navigationguide.ui as shown below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/050515f43029ff20a2f0a91ffca45209/href">https://medium.com/media/050515f43029ff20a2f0a91ffca45209/href</a></iframe><p>Once the package is created, we are ready to start creating the ui screens. For each of the ui screens, we will be creation 5 different Kotlin files.</p><h4>7. Create Entry Screen</h4><p>To create the Entry composable, right click the package com.example.navigationguide.ui.screens -&gt; New -&gt; Kotlin Class/File and name it Entry.kt</p><p>The Entry screen with have 3 components:</p><ul><li>Text component that says ‘Welcome to Navigation Guide’</li><li>A ‘Log In’ Button component</li><li>A ‘Register’ hyperlink text component</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/44beb65c21520780c9a7917fdb7f19d6/href">https://medium.com/media/44beb65c21520780c9a7917fdb7f19d6/href</a></iframe><h4>8. Create the Login Screen</h4><p>To create the Login composable, right click the package com.example.navigationguide.ui.screens -&gt; New -&gt; Kotlin Class/File and name it Login.kt</p><p>The Login screen with have 3 components:</p><ul><li>Text component that says ‘Log In’</li><li>Text Input Field — Email Address</li><li>Text Input Field — Username</li><li>A ‘Continue’ button to navigate to Welcome screen</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f33cf3aed71adabe524b8f0fdec4bf14/href">https://medium.com/media/f33cf3aed71adabe524b8f0fdec4bf14/href</a></iframe><h4>9. Create the Register Screen</h4><p>To create the Register composable, right click the package com.example.navigationguide.ui.screens -&gt; New -&gt; Kotlin Class/File and name it Register.kt</p><p>The Register screen with have 3 components:</p><ul><li>Text component that says ‘Registration’</li><li>Text Input Field — Email Address</li><li>Text Input Field — Username</li><li>Text Input Field — First Name</li><li>Text Input Field — Last Name</li><li>A ‘Register’ button to navigate to Welcome screen</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa81f6a23b48d7bf642825eac7539f09/href">https://medium.com/media/fa81f6a23b48d7bf642825eac7539f09/href</a></iframe><h4>10. Create the Welcome Screen</h4><p>To create the Welcome composable, right click the package com.example.navigationguide.ui.screens -&gt; New -&gt; Kotlin Class/File and name it Welcome.kt</p><p>The Welcome screen with have 3 components:</p><ul><li>Text component that says ‘Welcome’</li><li>Text component to display the Username from previous screen</li><li>A ‘Log Out’ button to navigate to Logout screen</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1727853e1d597fe529606271fa2e5d1/href">https://medium.com/media/e1727853e1d597fe529606271fa2e5d1/href</a></iframe><h4>11. Create the Logout Screen</h4><p>To create the Logout composable, right click the package com.example.navigationguide.ui.screens -&gt; New -&gt; Kotlin Class/File and name it Logout.kt</p><p>The Logout screen with have 3 components:</p><ul><li>Text component that says ‘Thanks You are now LOGGED OUT’</li><li>A ‘Log In’ button to navigate back to Log In screen</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d37b577db8ef0524c0a11309bba7518d/href">https://medium.com/media/d37b577db8ef0524c0a11309bba7518d/href</a></iframe><h3>All UI screens preview</h3><p>The build and refresh will show each of the screen that we coded about in the Preview Pane. The preview screens shows us that we were able to create the screens very much like the wireframes that we had initially drawn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JV088nYCcTvaoDzS0bOFmQ.png" /></figure><h4>12. Create and Invoke the Navigation Host</h4><p>The routes as well as the screens have now been created, now it is time to create the Navigation Host (NavHost) that links the NavController with the navigation graph that we created in the search class NavigationRoutes.</p><p>We will create a new Kotlin file named SetupNavigation.kt in the package com.example.todocompose.navigation and define a new Composable function that take the NavController as a input.</p><p>As you can see from the code, the Welcome composable expects the username from either the Registration screen or the Login screen, but we have not added code to pass it while invoking the Welcome composable. We will first define the composable for NavHost. The sealed class NavigationRoutes is used here create a navigation graph for the NavHost to invoke the screen and navigate to the right composable.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8898ecd4e8c0bb505412d463d1dc32d/href">https://medium.com/media/e8898ecd4e8c0bb505412d463d1dc32d/href</a></iframe><p>Once the SetupNavigation composable function is defined, we will add it to the MainActivity Class to link the NavHostController to the NavHost.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e31623de8bf13541f4c91d6c4fcef40/href">https://medium.com/media/9e31623de8bf13541f4c91d6c4fcef40/href</a></iframe><h4>13. Adding Navigation instructions to button clicks</h4><p>Every button in each of the 5 screen initiates navigation in our application. The Button components have a onClick attribute that we will use to navigate to the destination using the navigate() method in the instance of NavHostController. Starting with Entry.kt, we will add the navigation code to the onClick property using the respective routes.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f56a8905b2f61edcdf951769be444426/href">https://medium.com/media/f56a8905b2f61edcdf951769be444426/href</a></iframe><p>The Welcome screen expects to receive the username from the Login screen and Register screen to display the welcome message. This username needs to be appended to the route in the navigate() method call. The Welcome screen can access the appended username value from the route url using the navigation back stage entry.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dcd46a834af7a01206110d9126754f9d/href">https://medium.com/media/dcd46a834af7a01206110d9126754f9d/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/16901175792b6b6b39f042156e366ea5/href">https://medium.com/media/16901175792b6b6b39f042156e366ea5/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/94ed3d04b3dffb20f1862b223a305628/href">https://medium.com/media/94ed3d04b3dffb20f1862b223a305628/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc78a30b2634be9fdd531be2b3a49e88/href">https://medium.com/media/fc78a30b2634be9fdd531be2b3a49e88/href</a></iframe><h4>14. Extract &amp; Pass username from navigation back stage entry to Welcome screen</h4><p>The Login screen and Register screen is expected to pass on the username from the respective text fields and append to the routing url. The NavHost that was implemented in SetupNavigation.kt can access the username from the navigation back stage entry and pass the username into the Welcome composable.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c80a96ab1cd3696cb7b36a7d779f937a/href">https://medium.com/media/c80a96ab1cd3696cb7b36a7d779f937a/href</a></iframe><h4>15. Wow! We are finally done. Testing Time</h4><p>Now we are done with all of the basic coding. Its time to test our code and see the navigation component in action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/284/1*gYOuWLPsHoxbsj_Wgie8-w.gif" /></figure><h3>Conclusion</h3><p>This whole exercise of writing this story along with my learning has been really satisfying. I was unable to find a good step by step guide and explanation of implementing navigation in Jetpack compose and I started to write the story to help anyone else who is interested to learn the same.</p><p>Following are the next step by step stories in my plan:</p><ul><li>Room Database with Jetpack compose</li><li>Dependency Injection using Dagger Hilt in Andriod Jetpack project</li><li>Navigation Drawer with Jetpack compose</li></ul><p>Please feel free to ask questions or provide feedback regarding this story. I’m learning and always willing to make changes and adapt based on feedback and suggestions. Hopefully some of this will be help some readers while we all continue to learn together.</p><p>All the best!! and please ask questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5122b3dbfe73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting with Jetpack compose — Setting up Android Studio — Beginner Steps]]></title>
            <link>https://sajucrajan.medium.com/starting-with-jetpack-compose-setting-up-android-studio-beginner-steps-dc908a50484c?source=rss-4b35dd4c6eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc908a50484c</guid>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-studio]]></category>
            <dc:creator><![CDATA[Chacko]]></dc:creator>
            <pubDate>Wed, 04 Jan 2023 19:17:57 GMT</pubDate>
            <atom:updated>2023-01-04T19:20:37.689Z</atom:updated>
            <content:encoded><![CDATA[<h3>Starting with Jetpack compose — Setting up Android Studio — Beginner Steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thwJhiLGz8hHH_JP03EAdg.png" /><figcaption>Credit: <a href="https://android-developers.googleblog.com/2022/05/whats-new-in-jetpack-compose.html">https://android-developers.googleblog.com/2022/05/whats-new-in-jetpack-compose.html</a></figcaption></figure><p>I started to write my first article in medium.com since I found it very difficult to find any good guide that explains navigation and its components while implementing Navigation component in Jetpack compose. But as I started with the articles, I realized that I was assuming that all the readers know how to use Android Studio and maybe that assumption was incorrect. So I thought, though setting Android Studio is simple and easy, I should still create a Step by Step guide and walkthrough that will help a new interested Android developer to setup their machine.</p><p>Jetpack Compose is Android’s modern toolkit for simplifying and accelerating Android UI development. Jetpack reduces code and provides powerful tools using intuitive Kotlin APIs and built-in support for Material Design, Dark theme, animations, and more.</p><blockquote>Jetpack compose makes use of Kotlin features such as coroutines, and many methods that are supported only by a Kotlin compiler. It is not possible to code Jetpack components in Java and most probably not future plans to support Java for Jetpack compose. So to develop an app in Android Studio using Jetpack compose, you will need to learn or know a little but of Kotlin programming language.</blockquote><blockquote>But, I am also a firm believer that a programming language is never an issue for a programmer. All that is required is common sense and logic. So it does not matter if your know Kotlin or not. All you need is the will to learn and you’ll be able to start working in Jetpack compose and Kotlin. Start Learning <a href="https://developer.android.com/jetpack/compose/kotlin">Kotlin for Jetpack Compose HERE.</a></blockquote><h4>Following are the steps start with Jetpack Compose &amp; Android Studio</h4><h4>1. Download and install Android Studio</h4><p>The environment and tool to develop native Android app is provided in the Android Studio. It is an IDE (Integrated Development Environment) that includes the required software development kits, code editor, UI design visualization, phone emulators and debugging capability. The JDK that is required for comes packaged in the Andriod studio installer.</p><p>You can download and install the Android Studio from <a href="https://developer.android.com/studio">Android Developer site.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*ykJT1v5rC2LWFijwhty8AA.png" /><figcaption>Completing Android Studio Setup Screen</figcaption></figure><h4>2. Create a New Project using Jetpack</h4><p>Start the Android Studio application and you will be greeted with a Welcome to Android Studio screen. Since we are learning how to create a new application click on <strong>Create a New Project</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*3iRMzn5_uWbDKAyFfbZUag.png" /><figcaption>Welcome to Android Studio Screen</figcaption></figure><p>Android studio provides some prebuilt templates (Activity) that is a really good starting point for developing applications. Select the <strong>Empty Compose Activity </strong>from the options and click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5hgy1Kj6eBC3m3iSAaFbw.png" /></figure><blockquote>An activity is the entry point for an android application in its interaction with the user. The main activity will be the first screen to appear when a user launches the application. The Empty Compose Activity that we selected above will be the Main Activity for our application.</blockquote><p>As a final step before creating the project, you will have to provide the <strong>Name </strong>of the project. Here I provide the name as <strong>Navigation Guide</strong>. Lets not fuss about the package name at this point. You can also notice here that the <strong>Language</strong> is disabled and <strong>Kotlin </strong>is preselected. This is because only Kotlin is supported as a programming language for <strong>Jetpack Compose Activity</strong>. The last option is the Minimum SDK and this mentions the minimum Android version in which our application needs to work on. You can select API 21 a.k.a. Android Lollipop as the Minimum SDK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rvev_-0u-ysFq-P4c8JDvw.png" /></figure><h4>3. Explore the Android Studio UI</h4><p>The Android Studio by default opens the <strong>MainActivity.kt</strong>. It also generates broiler plate code that is displays ‘<strong>Hello Andriod</strong>’. The basic building block on a UI in Compose is the Composable function.</p><p>We can see that there are two functions that have the @Composableannotation. These functions let you define your app’s UI programmatically by describing how it should look rather than focusing on the process of the UI’s construction. To create a composable function, just add the @Composable annotation to the function name. The annotation is what lets the Android Studio know that its a function that displays something in the UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gBQDsBClkG3GGFss-ya98g.png" /></figure><p>There is also one another annotation @Preview that allows us to preview the UI without running the app in an emulator. On the top right of the Android Studio, you will notice a set of buttons (<strong>Code | Split | Design</strong>). The Split option allows us to visualize the composable that is invoked in the function with the @Preview annotation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*QD7la6S2lAtBMKcu7W7hvQ.png" /></figure><p>You will need to ‘<strong>Build and Refresh</strong>’ once before the UI is visible in the design section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ErgDkq2jowT7NRsgSu6poQ.png" /></figure><blockquote>Jetpack compose provides building blocks like Buttons, Texts, Images and much more, that provides easy and faster way to build a UI. In the above example we are only using the Text composable.</blockquote><p>In addition to the generated code, we will add the following code. The changes here is that we wrapped the Text composable inside of a Column composable to allow to align horizontally and vertically. As you go deeper into Jetpack compose you will learn about Row and Column composable and how the alignment and arrangement are interchangeable. We also changed the settings for the Column composable to fill the whole size of the screen and increased the size of the font to 30.sp.</p><pre>@Composable<br>fun Greeting(name: String) {<br>    Column(<br>        horizontalAlignment = Alignment.CenterHorizontally,<br>        verticalArrangement = Arrangement.Center,<br>        modifier = Modifier.fillMaxSize()<br>    ) {<br>        Text(text = &quot;Hello $name!&quot;, fontSize = 30.sp)<br>    }<br>}</pre><p>Please build and refresh once more to see the effect of the changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_jCXzz552aHFquvwGxRog.png" /></figure><h4>4. Running the application on the Android Emulator</h4><p>To run an application on an emulator, we need to setup a device on our machine. Select the Device Manager as shown in the screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*i7h1H_pbUZLFwkoS5KfHpQ.png" /></figure><p>Click on <strong>Create virtual device </strong>to start creating the android device for emulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*afUFxAkeyOSY7Y7ypzpaHw.png" /></figure><p>I select the Pixel 6 Pro since I used to own one before I upgrades to Pixel 7.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*535DdlhNWhPlaPzLHwGZlQ.png" /></figure><p>Select the Android OS version that you would like the device to run on. I had to download the Tiramisu API 33 Release. This download might take some time based on the speed of your internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*qydsA-MZl5NEFw0E5AnPAQ.png" /></figure><p>Click <strong>Finish</strong> and complete the device setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*QYIQtYHBIaeYWi3ac9RIBQ.png" /></figure><p>Click on the Run ‘app’ or Shift+F10 to run the application on the newly setup device. You can see both the preview as well as the emulator running together. Once the emulator is running you can switch back to Code view from the options on the top right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Q6n3ozlLR3X3KQ5jkfL_A.png" /><figcaption>Both Preview and Emulator Screens together</figcaption></figure><p>I hope this article was helpful and can help new interested developers to get started with Jetpack compose. I’m starting to like it and also enjoying sharing my experience and steps that I followed to start learning Android development using Jetpack compose in Kotlin.</p><p>Following are some of the stories that I have published and available to read:</p><ul><li><a href="https://medium.com/@sajucrajan/jetpack-compose-android-navigation-component-beginner-steps-part-1-theory-54b5b251fa00"><strong>Jetpack Compose — Android — Navigation Component — Beginner Steps — Part 1 (Theory)</strong></a></li></ul><p>More official documentation from Android Developer site :</p><ol><li><a href="https://developer.android.com/jetpack/compose">Build better apps faster with Jetpack Compose</a></li><li><a href="https://developer.android.com/jetpack/compose/documentation">Get started with Jetpack Compose</a></li><li><a href="https://developer.android.com/jetpack/compose/mental-model">Thinking in Compose</a></li><li><a href="https://developer.android.com/courses/android-basics-compose/course">Android Basics with Compose</a></li><li><a href="https://developer.android.com/jetpack/compose/tutorial">Jetpack Compose Tutorial</a></li><li><a href="https://foso.github.io/Jetpack-Compose-Playground/">Jetpack Compose Playground</a></li></ol><p>Thanks for reading. I’m a new writer on Medium or anywhere :-). Please share your thoughts and comments. Appreciate your feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc908a50484c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>