<?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 Sarath Kumar on Medium]]></title>
        <description><![CDATA[Stories by Sarath Kumar on Medium]]></description>
        <link>https://medium.com/@sarathrajendran?source=rss-7999b4e59e69------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QDB2bFe-TTSLgYmjcc1cvQ.jpeg</url>
            <title>Stories by Sarath Kumar on Medium</title>
            <link>https://medium.com/@sarathrajendran?source=rss-7999b4e59e69------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:08:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sarathrajendran/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[Finalise a Feature — The Methodologies]]></title>
            <link>https://sarathrajendran.medium.com/finalise-a-feature-the-methodologies-48513daa8baa?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/48513daa8baa</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Mon, 05 Jun 2023 14:11:49 GMT</pubDate>
            <atom:updated>2023-06-05T14:11:49.354Z</atom:updated>
            <content:encoded><![CDATA[<h3>Finalise a Feature — The Methodologies</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7YP4nZTS0GvTHa2esBEJw.png" /></figure><p>If you are ever curious about how we arrive at a solution, like how we can be sure that it is going to work out, there certainly have to be matrices for validating anything.</p><p>Similarly, we have methodologies that utilise different matrices to validate and finalise features in a product or the entire product.</p><p>Let’s discuss three simple and famous frameworks here which I personally prefer (explained in simple terms):</p><ol><li>Kano Model</li><li>MoSCoW</li><li>Value vs Effort</li></ol><h4>Kano Model (Kah-no)</h4><p>This method primarily takes customer satisfaction as the metric and prioritises features based on that.</p><p>Here is the graph representation,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*fvQK6yQgluxt1LFNd8AUrw.png" /></figure><p><strong>Must-Have or Basic Features:</strong> Without these features, customers will be highly disappointed.</p><p><strong>Performance Features:</strong> These features are directly correlated with customer satisfaction.</p><p><strong>Attractive or Delightful Features:</strong> These features bring the highest level of customer satisfaction and elevate the product to a leading position.</p><h4>MoSCoW</h4><p>MoSCoW stands for Must Have, Should Have, Could Have, and Won’t Have.</p><p>An example of MoSCoW is,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5tujyDwj5R4jGKi8UzclQ.jpeg" /></figure><p><strong>Must-Have features:</strong> These are non-negotiable and basic features that are essential for the targeted customer segment.</p><p><strong>Should-Have Features:</strong> These are important features that will add significant value to the product.</p><p><strong>Could-Have:</strong> These are the nice-to-have features that will have a positive impact.</p><p><strong>Won’t Have: </strong>The features falling under this category won’t be included in the roadmap, either due to lack of feasibility, or resources, or being too futuristic.</p><h4>Value vs Effort</h4><p>As the name says, Value vs Effort considers the value of the features vs the effort it takes to build.</p><p>Here is how it looks,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*a9klcUnkjRdZ3wyBdLrLkQ.png" /></figure><p>It has four quadrants:</p><ol><li><strong>High Value, Low Effort </strong>— These are easy wins, and a product must prioritise these features as a first step.</li><li><strong>High Value, High Effort</strong> — These features should be pursued after the easy win features, as they will significantly enhance the product.</li><li><strong>Low Value, Low Effort</strong> — Mostly, these are nice-to-have features that have a minimal impact.</li><li><strong>Low Value, High Effort</strong> — A product should avoid investing in these features unless all the other three categories have been addressed.</li></ol><h4>Why is a prioritisation framework important?</h4><ul><li>A prioritisation framework plays a vital role in decision-making.</li><li>The framework lets us focus on the important features which will improve customer satisfaction.</li><li>It will help us align with the right vision.</li><li>It will help us to allocate and manage the resources in an efficient manner.</li></ul><blockquote>Without an order to things, surely it will end in disaster. These frameworks are not just helping us with features, they help us in real life too.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48513daa8baa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Problem-Solution Fit & Product-Market Fit]]></title>
            <link>https://sarathrajendran.medium.com/problem-solution-fit-product-market-fit-b934344eccc5?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/b934344eccc5</guid>
            <category><![CDATA[problems-and-solutions]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Thu, 19 Jan 2023 17:06:59 GMT</pubDate>
            <atom:updated>2023-01-19T17:06:59.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w73bcQLJN-2liK8GnAMxJQ.png" /></figure><p>Have you ever wondered how new products are discovered? And what it is we have to do before building a product?</p><p>To begin with a product, you have a checklist to tick:</p><ol><li><strong>Desirable</strong> — Do customers want this?</li><li><strong>Feasible</strong> — Can we do this?</li><li><strong>Viable</strong> — Should we do this?</li></ol><p>The most important and initial part of any product’s life cycle is the Problem-Solution Fit and Product-Market Fit phases. In those phases, we check the <strong>desirability, feasibility, and viability</strong> of the product.</p><h3>What is PSF &amp; PMF?</h3><p><strong>PSF: </strong>Every product solves a unique problem statement. Nonetheless, not all problems are worth solving. In the PSF phase, we find if the product is desirable by getting answers to the following questions</p><ol><li>Is this a problem worth solving?</li><li>Do we have a solution to that problem?</li></ol><p><strong>PMF:</strong> It is the most important milestone of a product. In simple words, we check whether we are in the right market with the right product or not. In PMF, we find out if the product is viable and feasible</p><ol><li>Viable — Is it profitable?</li><li>Feasible — Can we build and scale it?</li></ol><p>Innovation is where your product lies. Here is a diagram for a better understanding of this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sm-F8MgKYwkLQRNEVfaCtg.png" /></figure><h4>How do we do this?</h4><p>We check the Problem Solution Fit followed by the Product Market Fit. This is an iterative process where we<strong> build-measure-learn.</strong></p><p>We will propose a solution (<em>which is a hypothesis for now as it has not yet been tested with the customers</em>) and slowly start converting it into a product.</p><p>Initially, the solution hypothesis will have the maximum uncertainty which we reduce eventually through the build-measure-learn process.</p><p>The cycle of PSF and PMF is</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xSGTRJINUTKPWDnVTrwt0A.png" /></figure><p><em>PoC — Proof of Concept, MVP — Minimum Viable Product</em></p><p>We identify the problem (<strong>build</strong>), test it with customers (<strong>measure</strong>), get the insights from the feedback (<strong>learn</strong>) and move to the next step or redo the current step (<strong>build again</strong>).</p><p>We do the <strong>build-measure-learn</strong> at every step of the cycle.</p><p>As soon the MVP is ready (<strong>build</strong>), the Product-Market Fit phase starts. We have to release it at the right market at the right time and see how it solves the customer’s need (<strong>measure</strong>), and get insights (<strong>learn</strong>) to improve it further. We will find out whether <strong>our solution is viable</strong> (profitable) at this phase, which paves the way for a stable business model.</p><p>The next phase after PSF &amp; PMF will be scaling and retention in the market which will be separate topics.</p><h4>Things to remember during these phases</h4><ol><li>Do the minimum experimentation to learn the most.</li><li>Instead of building what the customer wants, understand the problem statement and build a solution that the customer actually needs (Fall in love with the problem, not with the solution).</li><li>Infrastructure should grow along with the customer base</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b934344eccc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What, Why, and How of OAuth2?]]></title>
            <link>https://sarathrajendran.medium.com/what-why-and-how-of-oauth2-ba6a1ce4eeed?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba6a1ce4eeed</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[https]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[oauth2]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Sat, 21 May 2022 16:53:35 GMT</pubDate>
            <atom:updated>2022-05-22T09:38:48.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2QrHNz8rYnd1BKvH4qyBw.png" /></figure><p>I have been working with OAuth2 for nearly half a decade. All I wanted is a simple and clear document explaining the three questions in the title. Let’s get into the answers to the questions.</p><h4>What is OAuth2?</h4><p>OAuth2 is a way of authentication/authorization. We need to authenticate an API as we need privacy for our data.</p><blockquote>I can’t allow my friends to ready my chats</blockquote><h4>Why is OAuth2?</h4><p>OAuth2 is the best way to authenticate an API. It eliminates the pitfalls in Basic, API Key, and OAuth1 Authentication methods.</p><p>Before how? Let’s have a glimpse at the other two types of API authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFXT-fkIWlykkZUlRgcj9w.png" /></figure><h4>Basic Authentication:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BIZZXKlxpQZHckjFmTTU7w.png" /></figure><p>Here, we send our credentials (username &amp; password) in every request in the headers to authenticate. Anyone can just intercept and get your credentials easily.</p><blockquote>Your secret is no more a secret</blockquote><h4>API Key Authentication:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*USeIYHXW_vvn9ElUPrmLjg.png" /></figure><p>This time, the resource server will give an encrypted secret key. We should send the key in every request to fetch the data. Wait! Even now I can get the API Key and steal all your data as the API key is valid forever. Maybe until I close my account.</p><blockquote>Still, the secret is not maintained as a secret</blockquote><p>Here comes OAuth2,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*cu-KE-JDS4VDvlh4AEWtBQ.gif" /></figure><p>To make the process a bit complicated and <strong>the data secured.</strong></p><h4>How is OAuth2?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n8M9ayYXRbOzdIIrBDDsQg.png" /><figcaption>For a better understanding, I’ve split the process into nine steps.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XnqMWBinoOFjaaBE2L2V8g.png" /><figcaption>Terms used.</figcaption></figure><p>The zeroth step is, registering the client. The Client Application should register at the authorization server with a <strong>name, homepage, and redirect URL.</strong></p><p>On successful registration, the client will get a <strong>client ID and client secret. </strong>Which is used by the authorization server to identify the client.</p><p>Let’s get into the steps,</p><p><strong>1. </strong>The user is logging in to an App to see his data.</p><p><strong>2. </strong>The App (Registered Client) sends a request to the authorization server to identify the user. In this request, the client ID, client secret, redirect URI, and <strong>scopes </strong>are sent. Scopes are defined by the resource server and are used to identify what type of data the client wants to access.</p><p><strong>3.1.</strong> If the client details are correct, the authorization server will <strong>authenticate </strong>the user by logging in. <br><strong>3.2. </strong>On successful login, a consent page will be shown where the <strong>user authorizes </strong>the client to access the data.</p><p><strong>4. </strong>After authentication &amp; authorization the client app will receive a <strong>grant token/authorization code</strong>. Which holds the reference to the user permitted data.</p><p><strong>5 &amp; 6. </strong>Now, the client will send a request to the authorization server for the <strong>access token. </strong>In the request,<strong> authorization code/grant token, client ID, client secret, and redirect URI </strong>will be sent. Along with the access token, <strong>a refresh token </strong>can be generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n494jqN5LGCeWo_8sLZIaw.png" /></figure><p><strong>7 &amp; 8. </strong>Now the client can send a request to the resource server and <strong>fetch data</strong> using the access token. The resource server will communicate with the authorization server to do the token validation.</p><p><strong>9. </strong>If the user is <strong>logging out</strong> from the app/client, the refresh token will be revoked.</p><blockquote>If the access token expires, steps 5 &amp; 6 will be repeated with the refresh token.<br>Steps 7 &amp; 8 will be repeated by the client to fetch data from the resource server.</blockquote><p>OAuth 2.0 is the industry-standard protocol for authorization. Widely used by most the tech giants.</p><p>Thanks for reading, Happy Authenticating!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba6a1ce4eeed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do’s, Don’ts,  Tips in Swift -2]]></title>
            <link>https://sarathrajendran.medium.com/dos-don-ts-tips-in-swift-2-bfe87c15f062?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe87c15f062</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[swift-programming]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Sat, 17 Apr 2021 15:08:21 GMT</pubDate>
            <atom:updated>2021-04-17T15:08:21.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>Do’s, Don’ts, Tips in Swift -2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f6iASXAB1WkdjQyx.png" /></figure><p>A perfect start is the main key to the outcome. Before reading this, Kindly read the<a href="https://weirddev.medium.com/dont-do-this-when-you-write-code-in-swift-1-24a87c706dc9"> first part of this </a>if you haven’t read it yet.</p><h3>Let’s begin!</h3><h4>1. How to write a function?</h4><ul><li><strong>How?:</strong> You can write a function using keyword <strong>func </strong>keyword. Your code goes within the curly braces. Well, I’m not saying that.</li><li><strong>Then?: </strong>Strictly maintain<strong> </strong>the Single Responsibility Principle <strong>(SRP)</strong> while declaring a function. Don’t flood a function with too much code. Have separate functions for every work. It’s fine to have a function with a single line code if it makes sense.</li><li><strong>Name:</strong> Name a function apt to what it is actually doing. Never call a Postman to do the cleaning works, it should be the housekeeping!</li><li><strong>The Code: </strong>If you write a function that contains some business logic, validate the parameters at first, followed by the logic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wU94jdtDpzpnJNLHkKoE7A.png" /></figure><h4>2. Declaring view controller.</h4><ul><li><strong>Use: </strong>For declaring UI, Managing animation and responding to user input, implementing delegates and datasource, managing view’s data, navigation logic, etc… This is how we use the view controller.</li><li><strong>Separation: </strong>Use a separate model object for the following loading data, managing view’s data, deciding, and making navigation, delegates, and datasource with plenty of logic, performing animations, holding UI constants, etc...</li><li><strong>Avoid complications in UI: </strong>If your UI is too complicated, declare a separate view for complicated UI. Use Child ViewController as well if possible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D7ZE7QmD-65kqaXHotjF5A.png" /></figure><h4>3. Unknown case in decodable enum.</h4><ul><li><strong>Decodable enum: </strong>Enums are used when we know all possible values at compile time. And We (I) use Decodable enum for any API key that contains predefined values.</li><li><strong>Case: </strong>As changes are unpredictable, we may add or remove values to that key from API. We can have our cases synced with API only on our latest build. But the user would be still using an old version of our app.</li><li><strong>Unknown case: </strong>Declare an unknown case in the enum, by overriding the default decodable init. Show error or define logic for the unknown case.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dIsM22vbuAlrKetuq55_Ng.png" /></figure><h4>4. Debouncing.</h4><ul><li><strong>Case: </strong>User won’t be friendly to our app even it is a user-friendly app. So, avoid hitting API or doing something on every tap of the user.</li><li><strong>Example: </strong>If you have a search box, never hit an API for every key which the user enters.</li><li><strong>Solution: </strong>Use a debouncer class as below to avoid multiple requests. The Debouncer class goes like below.</li></ul><pre>final class Debouncer {</pre><pre>  private let timeInterval: TimeInterval<br>  private var timer: Timer?<br>  var handler: (() -&gt; ())?<br>  <br>  init(timeInterval: TimeInterval) {<br>    self.timeInterval = timeInterval<br>  }</pre><pre>  // Call the function after assigning value to the handler <br>  func renewInterval() {<br>   <br>   timer?.invalidate()<br>   timer = Timer.scheduledTimer(withTimeInterval: timeInterval, repeats: false, block: { [weak self] (timer) in<br>     self?.timeIntervalDidFinish(for: timer)<br>           })<br>  }</pre><pre> // Invalidate a scheduled call<br> func invalidate() {<br>   timer?.invalidate()<br> }</pre><pre> @objc private func timeIntervalDidFinish(for timer: Timer) { <br>   <br>   guard timer.isValid else { return }<br>   handler?()<br>   handler = nil<br> }</pre><pre>}</pre><ul><li><strong>Usage: </strong>Call the API or do the work in the handler block, and renew the debouncer whenever a new value is assigned.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVncobxDx6wwsO8If2fNgA.png" /></figure><p>I’ll be writing up on smart working extension for your codebase next. Stay tuned!</p><p>P.S: Clap? Ready to learn from your suggestions and feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe87c15f062" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t do this when you write code in Swift-1]]></title>
            <link>https://sarathrajendran.medium.com/dont-do-this-when-you-write-code-in-swift-1-24a87c706dc9?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/24a87c706dc9</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swift-programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Sun, 21 Mar 2021 19:15:17 GMT</pubDate>
            <atom:updated>2021-03-21T19:42:48.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1UKnuqF21UhbKx38.png" /></figure><p>I am ashamed whenever I look back at my code after few weeks. Even though it shows the progress, it’ll be killing when I add or refactor something to the code. Here are few things which will improve your coding and assist you to write <strong>Clean Code</strong>. I believe this will prevent you from that embarrassing moment I had.</p><h4><strong>What is a Clean Code?</strong></h4><ul><li>A code with well-structured architecture based on the project modules, which is effortless to modify, add, remove and replace any part of it. Easily readable and understandable.</li></ul><h4><strong>Why Clean Code?</strong></h4><ul><li>It doesn’t matter that you write code to an app that is trending or a fun-project. Think twice before writing any code regardless of its importance. You won’t be having time to refactor all the code you wrote when the world going with new updates and new features.</li><li>As we can’t predict the future of our life itself, we can’t define the roadmap of our project precisely. Our code should be the finest to incorporate any changes.</li><li>You’re not the only one who’s going to work on a project (Perhaps if you’re single). Write code that is surely readable and modifiable.</li></ul><blockquote>DON’T MESS WITH CODE, YOU’LL REGRET IT ONE DAY.</blockquote><p>This will be a series of blogs in which you’ll go through stuff that make your code better readable and organized. We will start with few basics tips in this series.</p><h3>Let’s get started!</h3><h4><strong>1. How to name a Delegate and its methods?</strong></h4><ul><li>Name delegate with the class name as the prefix.</li><li>Pass the class instance as the first parameter always, which helps the delegate to handle multiple instances.</li><li>Instead of just naming the delegate methods based on their purpose, have the name as the class name for methods with parameters.</li><li>Use the class name as the prefix for methods without any parameter other than the instance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BDc4c0u9sVr05CHHKcum0g.png" /></figure><h4><strong>2. Never regret writing an extension to a class.</strong></h4><p>Declare separate extensions whenever needed in the following cases.</p><ul><li><strong>Protocol Confirmation: </strong>Whenever conforming to a protocol, delegate, or a datasource use a separate extension with a pragma mark.</li><li><strong>Methods Grouping based on functionality: </strong>Group methods based on their functionality. For example group methods which are dealing with UI rendering, group methods which are performing animations.</li><li><strong>Grouping based on access: </strong>Declare a separate extension for public methods and private methods. Where you can easily jump there for publically exposed methods.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tt9yASwebhyEkrx6vm3Dkg.png" /></figure><h4><strong>3. Avoid strings and use enum in resource loading.</strong></h4><ul><li><strong>No Raw String:</strong> Do not use raw strings to load resources from assets. You have to modify it everywhere whenever you remove or modify a resource.</li><li><strong>Use Enum: </strong>Maintain an enum that has all the names of available assets. Declare a convenience constructor with the enum as the parameter.</li><li><strong>Advantage: </strong>You have to modify just the enum values based upon the changes.</li><li>Use <strong>_dark </strong>and <strong>_light </strong>suffix for assets that have different colors based on the system theme. Add the suffix along with the <strong>rawValue </strong>based on the theme.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTJqL_lMi7hxIGrg3q-0LA.png" /></figure><h4><strong>4. Grouping lines in a code block using local closure.</strong></h4><ul><li><strong>No use: </strong>When you declare a variable, it’ll be having a scope through the entire code block you declared it. Perhaps you just used it to declare some other constant. Where it has no-meaning of having scope for the entire code block.</li><li><strong>Closure: </strong>Declare a local closure, which holds the logic of creation and configuration of an object.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t0KBV-RPyhj5zDJHPLUbRw.png" /></figure><h4><strong>5. Spacing!!! Give space to take a breath.</strong></h4><ul><li>Spacing is the important thing which gives you a better reading. Which you have to give apt spacing.</li><li><strong>When?: </strong>Leave space only after comma and colon. Before and after curly braces. If you’re too lazy, use <strong>ctrl + i </strong>after selecting a code block, where Xcode will help you.</li><li><strong>In methods: </strong>Declare parameters on a new line if the method signature is too long. Group parameters if it makes sense. For example, instead of getting the width and height of a view as separate argument use <strong>CGSize </strong>as the parameter type.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4J8_kj5WQEKBBERlPlypA.png" /></figure><p>All things start with a small point, the above recommendations won’t be a big deal. But definitely, it’ll be one of the beautifiers for your code. Try it from the next line which you’ll be coding after reading this. Simply, if not now? then when?</p><p><strong><em>Stay tuned for the next one!</em></strong></p><p>P.S: Clap? Ready to learn from your suggestions and feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24a87c706dc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make your android activity class code better!]]></title>
            <link>https://sarathrajendran.medium.com/make-your-android-activity-class-code-better-c6b935182c77?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6b935182c77</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[android-activity]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Mon, 09 Dec 2019 17:14:32 GMT</pubDate>
            <atom:updated>2019-12-09T17:14:32.184Z</atom:updated>
            <content:encoded><![CDATA[<p>Better code, the best app, and non-stop growth.</p><p>Maintaining the codebase is a big challenge nowadays based on the project size and contributors count. A more reliable codebase and architecture will help us in the time of enlargement, long term maintenance, and alteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*nomEGXpCStMHTgTHoI0thQ.jpeg" /></figure><p>Here are some tips which make your android app fine and pretty good seeming.</p><h3>Activity/ Fragment View Holder.</h3><p>The activity has the supreme responsibility for the user-interactions and presenting the view. Dumbing too much of code in that would always mess up. Having all codes like UI, permission handling, user-interactions, and data fetch initializing in the same class, We can separate the whole UI part.</p><pre>public class MainActivity extends AppCompatActivity {</pre><pre>    private ConstraintLayout mainLayout;<br>    private TextView inputView;<br>    // and all your views will be a property of the class.</pre><pre>    @Override<br>    <strong>protected void </strong>onCreate(<strong>final </strong>Bundle savedInstanceState) {<br>       <strong>super</strong>.onCreate(savedInstanceState);<br>       setContentView(R.layout.<strong><em>activity_main</em></strong>);</pre><pre>       //here we will be initiating those properties by,<br>       mainLayout = findViewById(R.id.main_layout);</pre><pre>   }</pre><pre>   private void addTheme() {<br>     <br>    // if you have some ui rendering work in runtime. it will be taking place in the activity itself.</pre><pre>   }</pre><pre>}</pre><p>To get rid of All UI code in the activity. Create a class named <strong>{your_activity}ViewHolder. </strong>Now, the view holder of your activity is responsible for holding the reference of widgets. Not only the UI elements also doing UI related operations. To give an instance,</p><pre>pubilc class <strong>MainActivityViewHolder </strong>{</pre><pre>    private ConstraintLayout mainLayout;<br>    private TextView inputView;</pre><pre>    public MainActivityViewHolder(Activity activity) {</pre><pre>     // assign values to the properties;<br>    }</pre><pre> // all methods related to UI operations should take place in the activity view holder.</pre><pre>  void addTheme() {</pre><pre>  }<br>}</pre><pre>public class <strong>MainActivity</strong> {</pre><pre>   private MainActivityViewHolder viewHolder;</pre><pre>    @Override<br>    <strong>protected void </strong>onCreate(<strong>final </strong>Bundle savedInstanceState) {<br>       <strong>super</strong>.onCreate(savedInstanceState);<br>       setContentView(R.layout.<strong><em>activity_main</em></strong>);<br>       viewHolder = new MainActivityViewHolder(this);</pre><pre>    }<br>}</pre><p>Now, your activity class will be freed from UI codes. Do the same for the fragment too. As well as create your complicated custom views as a separate <strong>XML </strong>with a separate class for that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6b935182c77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Product Management? -1]]></title>
            <link>https://sarathrajendran.medium.com/what-is-product-management-1-7d04ff1417d9?source=rss-7999b4e59e69------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d04ff1417d9</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Sarath Kumar]]></dc:creator>
            <pubDate>Sat, 07 Dec 2019 10:27:24 GMT</pubDate>
            <atom:updated>2019-12-07T10:27:24.095Z</atom:updated>
            <content:encoded><![CDATA[<p>I hope here you’ll get a minimum of what is Product Management. Let’s dig through all later.</p><p>Let’s start with the great one by the great Martin Eriksson.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7pIQnYEdUvQpR_JFkc9c1A.png" /></figure><blockquote>Product Management is the intersection point among <strong>business</strong>, <strong>technology</strong> and <strong>user experience</strong> (UX).</blockquote><p>It is the point where <strong>what customers want </strong>and <strong>what developers can develop</strong>. It is the prime responsibility of the product manager to manage product development based on the customer’s requirements.</p><p><strong>Product Management </strong>revolves wholly around the customer. Because the market and customer needs define all the details about the product’s current and future requirements.</p><h4>Product Strategy</h4><p>Each product requires different goals, features, challenges, and targets that make product management principles vary from one product to another and one company to another. It will be the roadmap of the product with end-end vision.</p><p>A well-defined product strategy leads to a successful product. Before defining it you should be an expert about the company’s market, user personas, and competitors.</p><h4>Developing methodologies</h4><p>As I said product management involves <strong>what developers can actually develop. </strong>As a product manager, you should be proficiency in a minimum of one of the core knowledge fields and with a fair basic level of knowledge in the others.</p><p>Product management helping teams day-to-day tech developments towards the business goals and achieving the steady progression through the roadmap. Development succession should depend on the customer need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d04ff1417d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>