Yera

yera

167 Stories To Learn About Crypto Adoption

A DISCOURSE

THE NEW NAVIGATION AND DISCOVERY OF THE KINGDOM OF MUSCOVY

In this post I’m going to go over why if statements should be removed from your code. I’m not saying that you should go back and remove all if statements from all the code that you’ve written or start some major refactor. I’m just proposing a more human readable style of writing code. It’s easy to write code that works and executes. The machine doesn’t care how you structure your code or what you name your variables. The difficult part is writing code that other people can look at and quickly understand. This is better demonstrated with examples. Let’s take this piece of arbitrary code: This is a fairly simple example and shouldn’t take you very long to parse through. However, this simple little method can very quickly evolve into something that’s unmaintainable, infuriatingly hard to read and a nightmare to test. Not only can we make this more human readable but we can reduce the cyclomatic complexity of this method if we remove the if statements and abstract away some of the logic into simpler more terse/descriptive methods. business Image borrowed from Yeray Darias It’s relatively simple to get rid of these if statements and turn our simple example into a more declarative style. First, we can turn every expression inside our if’s into it’s own . function Our simple example is starting to shape up. Now, we can tell what those conditionals are checking for. Unit-testing just those conditionals is possible, too, since they’re encapsulated within their own methods. However, we can take this a step further… There’s that nasty loop in there. It sticks out like a sore thumb. We can get rid of it with a and abstract that logic away into it’s own method. forEach .map() While we’re at it, let’s get rid of both of those if statement. We can replace them with ternary operators. Again, simpler to just demonstrate: Conclusion Anyone who has to maintain this code is going to have a much easier time understanding what the method is doing. It’s also a lot easier to add on more methods into the article parse method, in comparison to how this file used to look like. getRelatedArticles parseRelatedArticle, Each of these methods performs a highly specific function which makes unit-testing this file much better. If an error occurs at run time the stack trace will tell you exactly which method failed, so this makes debugging much simpler than having to check what line failed and trace what exactly is happening through the original method. getRelatedArticles This, of course, is a completely arbitrary example. I trust that you’ll be able to extrapolate from this.

Human Readable Code or Why I Don’t Like if Statements

We are far from a world where people only engage with and consume pictures, videos, and text only created by professionals. TikTok, for example, has created some of the biggest names in the entertainment industry today from people that picked up a camera and pressed record. It has created an incredible opportunity for both consumers and brands. Brands continue to see the value in user-generated content and its use to build trust with their audience, spread their name, and grow their revenue. If you haven’t started already, collecting this valuable content being posted on social media or shared with your business and starting to repurpose it to benefit your business is crucial. What is UGC? User-generated content, or , is videos, pictures, texts, and other mediums created by your customers and published across social media or other channels. Here are some of the more common forms of UGC that can be found: UGC Reviews Videos i.e, unboxing videos or even product demonstrations Pictures i.e, wearing a brand’s clothing or using it in action Testimonials Podcasts Blog posts Why is UGC important? UGC content can be effectively used across all the stages of the buyer's journey to help engage them and build credibility with the brand. Competition amongst brands is fierce, and one of the best ways to attract more customers is to stand out from the rest and build trust with your prospects. agree that consumers trust content created by customers more than content created by a brand. Therefore, encouraging UGC ultimately helps your brand to grow a community, motivating your customers to share their thoughts and experiences with the product. 93% of marketers UGC can be a significant driver in the success of your brand by prompting purchasing decisions and increasing overall conversion rates. Don't miss out on the opportunities UGC offers, and start utilizing the methods we suggest below to collect your own. What GoPro has taught us about UGC is famous for its small, portable video cameras that thrill-seekers and adventurers love. GoPro is one of the most successful brands in taking advantage of the benefits of user-generated content. In doing so, they have amassed a large following of loyal customers that look forward to sharing their stories and videos to be posted across their social channels. GoPro With three million+ YouTube followers, GoPro constantly uploads user-generated content showing their customers using the product in action, whether it be surfing, traveling, race car driving, or even a wedding! GoPro has captured the hearts of its audience, inspiring them to purchase the product and create their own stories and videos to be shared with the like-minded community they’ve created. Tips for catching UGC content Gathering UGC content doesn’t have to be difficult. There are many different ways that you can try to encourage your pre-existing customers to create their own and share them. Here are some tips for catching UGC from customers: Ask for reviews and feedback Simply asking your customers for a review or feedback can go a long way towards gathering user-generated content and strengthening their relationship with the brand. Send emails, text messages, or make a post asking your customers to review your product or service and post it online. Many of your brand loyalists will often share their thoughts online for others to read. Customers will often be happy to support your business and provide feedback on their experiences. People like to have their voices heard, and it is up to you to provide the space for it. Start a #hashtag Hashtags are a great way to encourage customers to share content about your brand and its products. A great example of a successful hashtag is campaign. It urged users to post a picture wearing their iconic Mickey Ears with the hashtag in their caption– for every photo posted, Disney donated $5 to the Make-A-Wish Foundation. Disney’s #ShareYourEars The campaign was a huge success, with nearly 2 million people posting photos wearing the ears and sharing their thoughts on the brand’s positive contribution to society. As a result, Disney collected great user-generated content and made waves worldwide due to their charitable donation. Launch a contest or challenge Contests and challenges are another great way of motivating customers to share content about your brand online. For example, the contest can ask customers to post a photo to enter and win a prize chosen by your company. Sabra Hummus did a great example of this for . They asked people to share their favourite flavour of Sabra hummus, which took off on TikTok, with creators sharing videos about their favourite Sabra hummus, some videos professionally filmed, allowing Sabra to collect user-generated content they could continue to use across their channel for years to come! National Hummus Day Collecting UGC with Moast Moast enables brands to build communities of like-minded people that share content about their products to be viewed and discussed amongst prospective customers. With Moast, brands onboard customers to the platform so that prospective customers can ask questions, arrange meetups, and learn more about the company and its products. A brand's customers are asked to create profiles with a short bio and stories on how they use your product. They then can add posts, videos, and thoughts about their products and the brand. The result is a comprehensive collection of a brand’s best customers and their “user stories” featured on an interactive map. Moast is the perfect platform to collect user-generated content for your business. Customers can share their content, and you can repurpose it across your brand's channels. It's a great way to engage with your audience and share their experiences with others.

Acquiring UGC From Customers: A 2023 Playbook

Welcome to the chaotic realm of online shopping, where consumers are bombarded with an overwhelming number of choices and an avalanche of information. In this post, we'll dive into the messy online shopping experience and explore why consumers find themselves lost amidst a sea of options. Truly understanding where your consumer is coming from can drastically change and improve the way you position and sell your products online. From the trust crisis to the constant barrage of advertisements, we'll unravel the complexities and share some insights that shed light on this shopping frenzy. The Paradox of Choice It's a paradoxical reality: while having numerous options seems like a dream come true, it often leads to indecision and confusion. Research studies have shown that when faced with an excessive number of choices, consumers tend to experience decision fatigue, leading to dissatisfaction with their final selection. According to a conducted by psychologists Sheena Iyengar and Mark Lepper, too many choices can leave consumers feeling overwhelmed and less satisfied with their purchase. study To counter fatigue and make decision-making easier,  brands should provide clear and concise product information, including detailed descriptions, specifications, and customer reviews. This information should highlight key features, benefits, and use cases, enabling consumers to quickly assess the suitability of a product for their needs. One example of a brand that excels in providing clear and concise product information is Apple. Apple's website and product pages are known for their meticulous attention to detail and comprehensive information. Here's how they achieve this: Detailed Descriptions: Apple provides thorough descriptions of each product, highlighting its key features, technical specifications, and functionalities. They use concise and easily understandable language to communicate the product's capabilities and benefits. Interactive Visuals: Apple utilizes interactive visuals, including high-quality images, videos, and 360-degree product views, to showcase the product from various angles. This allows consumers to get a closer look at the product and its design, enhancing their understanding and assessment of its suitability. Use Cases and Examples: Apple includes real-world use cases and examples to demonstrate how their products can be integrated into customers' lives. They showcase different scenarios and highlight the benefits and solutions that the products offer, helping consumers envision the product's potential. Customer Reviews and Ratings: Apple incorporates customer reviews and ratings into their website, allowing potential buyers to read feedback from other users. This social proof helps build trust and provides additional insights into the product's performance and user experiences. Simplified Comparison: Apple facilitates product comparison by offering side-by-side comparisons on their website. This feature enables consumers to evaluate different models or configurations based on their specifications, helping them make more informed decisions. By presenting comprehensive product information in a user-friendly manner, Apple empowers consumers to quickly assess the suitability of their products and make confident purchase decisions. This approach contributes to a smoother online shopping experience, reducing the feeling of being overwhelmed by excessive choices. The trust crisis In the digital era, trust has become a valuable commodity. With countless online sellers vying for attention, consumers are rightfully cautious about whom to trust. They are no longer willing to rely solely on traditional advertising. Instead, they turn to fellow consumers for guidance. Online reviews have become the go-to resource for building trust. Sites like , , and offer platforms where shoppers can seek authentic feedback and opinions from real people who have experienced the product or service firsthand. YouTube Reddit Trustpilot But very quickly, shoppers end up with dozens of tabs open all at the same time browsing feedback from anonymous strangers online. And while sites like YouTube, Reddit, and Trustpilot provide valuable platforms for seeking feedback, opinions, and reviews, the abundance of information available can indeed become overwhelming for consumers. The sheer volume of content and varying perspectives can make it challenging to navigate and make confident decisions. With countless reviews, comments, and discussions available, consumers can feel inundated by an overwhelming amount of information. Processing and synthesizing this vast array of opinions can be time-consuming and mentally exhausting. To make things more complicated, different individuals have diverse experiences and preferences, leading to a wide range of opinions on products or services. Shoppers often encounter conflicting viewpoints, making it challenging to determine which sources to trust and which reviews align with their own needs and preferences. These online platforms also often contain subjective reviews influenced by personal biases, emotions, or even sponsored content. Consumers need to filter through biased or exaggerated opinions to find genuine and objective feedback that aligns with their decision-making process. Context is a less talked about but important factor: online reviews may lack the necessary context for consumers to fully assess their relevance to their specific situation. Factors such as the reviewer's background, expectations, or usage scenario may differ from their own, making it difficult to apply the information directly to their purchasing decision. The role of social media In the age of social media, brands are constantly competing for attention in users' feeds. While these platforms allow for targeted advertising, the incessant stream of ads can be overwhelming. Consumers find themselves bombarded with enticing offers and new options, making it increasingly challenging to filter through the noise. According to , the average person is exposed to more than 6,000 to 10,000 ads per day! This saturation of ads can lead to ad fatigue, making it difficult for consumers to find their "aha" moment (more on this below). Ad Lock To combat the constant stream of advertisements, consumers actively take measures to reduce ad exposure. They employ ad blockers, browser extensions or plugins that filter out intrusive ads during their online browsing. Additionally, consumers skip or fast-forward through ad breaks in videos and TV shows, utilizing features that allow them to bypass advertisements. Some choose to pay for ad-free versions of platforms or services, enjoying uninterrupted content for a fee. ‍ Consumers also selectively consume content on platforms that prioritize ad-free experiences, seeking out channels and services that align with their preferences. These actions reflect a growing desire among consumers to regain control over their online experiences and minimize the overwhelming presence of ads. Seeking Validation and the Proverbial “Aha” Moment To make informed decisions, consumers often seek validation from multiple sources. They browse social media pages, read product reviews, and ask for recommendations from friends. The desire for a magical realization, the "aha" moment when they discover a brand that resonates with them, drives them to gather as much information as possible. According to a survey by BrightLocal, 91% of consumers read online reviews regularly or occasionally to help them make purchasing decisions. These diverse sources of information can create both excitement and confusion, contributing to the overall messiness of the online shopping experience. ​​The quest for the elusive "aha" moment - that moment when consumers find a brand that truly resonates with them to the point where they’re ready to add-to-cart and checkout, fuels their desire to gather as much information as possible. Engaging in conversations with other customers becomes a valuable avenue for achieving this magical realization more quickly. By actively seeking out the experiences and opinions of fellow shoppers, consumers can tap into real-world insights that go beyond marketing messages. That’s where a platform that facilitates these conversations like Moast becomes critical to a brand’s online shopping journey. Engaging in these conversations allows consumers to gain a deeper understanding of how a brand's products align with their needs, preferences, and values. It enables them to leverage the collective wisdom of other customers, accelerating the process of finding that "aha" moment and discovering a brand that feels just right. Conclusion Online shopping, while convenient, can be an overwhelming journey. The surplus of options, the trust crisis, and the constant barrage of advertisements all contribute to the messy nature of the experience. As consumers, it's important to be mindful of the challenges and take steps to navigate this jungle effectively. Brands, on the other hand, must strive to build trust, offer personalized experiences, and simplify the decision-making process for their customers. In this digital age, where messiness seems to prevail, let's embrace the adventure of online shopping, armed with the knowledge and tools to make informed choices and find that magical "aha" moment amidst the chaos.

How Science Can Help Overcome the Messy Online Shopping Experience

AsyncIO for the Working Python Developer

I used to really love programming. I didn't really like it during my early college years, but I started to really like it later on when I started to get a good grasp on coding and was able to build my ideas. I love the feeling when I'm getting in the zone and start hyper-focusing on coding. Late in college, I started to make money by doing the projects of my classmates and by freelancing until I got hired to work full-time by a company with a great salary. And then I started to be interested in building side projects. Over the years, I have built many side projects where like 95% of them have failed. I say the other 5% were kinda successful because they gained users and 1 side project gained a paying customer. It was a cycle of coming up with an idea, building it, launching and failing then starting over again. This stopped completely when I got burned out from work (and probably because of the frustration that most of my side projects failed and didn't get any traction). After years of job hopping, I started working for a startup for years and made great money that allowed me to buy a car and a house and have a comfortable life. Working on this startup was very tiring though because I was working for very long hours per day and work consumes the majority of my time daily. Overworking for a few years got me so burnt out that I started hating my job and started to lose my passion and interest in coding and completely stopped building side projects. The burnout lasted for 6 years. For some reason, this year, I feel like I'm starting to recover from burnout and got interested in coding and building side projects again. It's probably because I significantly reduced the hours that I work per day (a few years where I probably only work for ~4 hours on weekdays) and started to consistently exercise and improve my diet for almost a year. I recently started to build side projects again; to get the ball rolling, I just started to build simple websites or web apps that I can build very quickly like a speech to polished notes web app and a calm jobs website that scrapes job posts and calculates a work-life balance score to help job seekers find jobs with better work-life balance. My personal experience of burnout inspired me to build it. After these initial side projects, I plan to start building more complicated ones. Has anyone else gone through something similar? How did you rediscover your love for programming? I used to really love programming. I didn't really like it during my early college years, but I started to really like it later on when I started to get a good grasp on coding and was able to build my ideas. I love the feeling when I'm getting in the zone and start hyper-focusing on coding. Late in college, I started to make money by doing the projects of my classmates and by freelancing until I got hired to work full-time by a company with a great salary. And then I started to be interested in building side projects. Over the years, I have built many side projects where like 95% of them have failed. I say the other 5% were kinda successful because they gained users and 1 side project gained a paying customer. It was a cycle of coming up with an idea, building it, launching and failing then starting over again. This stopped completely when I got burned out from work (and probably because of the frustration that most of my side projects failed and didn't get any traction). After years of job hopping, I started working for a startup for years and made great money that allowed me to buy a car and a house and have a comfortable life. Working on this startup was very tiring though because I was working for very long hours per day and work consumes the majority of my time daily. Overworking for a few years got me so burnt out that I started hating my job and started to lose my passion and interest in coding and completely stopped building side projects. The burnout lasted for 6 years. For some reason, this year, I feel like I'm starting to recover from burnout and got interested in coding and building side projects again. It's probably because I significantly reduced the hours that I work per day (a few years where I probably only work for ~4 hours on weekdays) and started to consistently exercise and improve my diet for almost a year. I recently started to build side projects again; to get the ball rolling, I just started to build simple websites or web apps that I can build very quickly like a speech to polished notes web app and a calm jobs website that scrapes job posts and calculates a work-life balance score to help job seekers find jobs with better work-life balance. calm jobs My personal experience of burnout inspired me to build it. After these initial side projects, I plan to start building more complicated ones. Has anyone else gone through something similar? How did you rediscover your love for programming?

6 Years of Burnout: My Journey Back to Loving Programming

My 3-Year Freelancing Journey: How I completed 1200 Projects and Earned the Big Bucks

আমার 3-বছরের ফ্রিল্যান্সিং জার্নি: আমি কিভাবে 1200টি প্রজেক্ট সম্পূর্ণ করেছি এবং বিগ বক্স অর্জন করেছি

Meine 3-jährige freiberufliche Reise: Wie ich 1200 Projekte abschloss und das große Geld verdiente

Mi viaje de tres años como autónomo: cómo completé 1200 proyectos y gané mucho dinero

Mon parcours indépendant de 3 ans : comment j'ai réalisé 1 200 projets et gagné beaucoup d'argent

मेरी 3 साल की फ्रीलांसिंग यात्रा: कैसे मैंने 1200 प्रोजेक्ट पूरे किए और मोटी कमाई की

私の3年間のフリーランスの旅: 1200のプロジェクトを完了して大金を稼いだ方法

나의 3년 프리랜서 생활: 1200개의 프로젝트를 완료하고 큰 돈을 버는 방법

Minha jornada de freelancer de 3 anos: como concluí 1.200 projetos e ganhei muito dinheiro

Мой трехлетний путь фрилансера: как я выполнил 1200 проектов и заработал большие деньги

3 Yıllık Freelance Çalışma Yolculuğum: 1200 Projeyi Nasıl Tamamladım ve Büyük Paraları Nasıl Kazandım

Hành trình 3 năm làm việc tự do của tôi: Tôi đã hoàn thành 1200 dự án như thế nào và kiếm được số tiền lớn

我的三年自由职业之旅：我如何完成 1200 个项目并赚大钱

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 This is Part 5 of our SDK development series where we get a CDN of our SDK Contents: ⚡ Getting CDN
⚡ Integrating CDN and testing SDK Step 1: Get a CDN Head over to https://www.jsdelivr.com/, and search for your NPM package. Choose the default version, and copy the link. Head over to the Test Browser app, and integrate the CDN: <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="https://cdn.jsdelivr.net/npm/ts-lib-template-starter@1.0.0/dist/index.global.min.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> Open the file, and see the result: Step 2: Getting the Latest CDN Version Always Put @latest instead of the version to always fetch the latest CDN version https://cdn.jsdelivr.net/npm/ts-lib-template-starter@latest/dist/index.global.min.js Sometimes, when a new version of SDK is published, jsDeliver takes a few minutes to a few days to point @latest version to the updated version. To fix this, when you publish a new version, head over to https://www.jsdelivr.com/tools/purge, and enter the link of the CDN like: This will purge the cache and point @latest version to the updated version. Wrapping Up: We just completed the steps to get a CDN of our SDK. Stay tuned for further parts to dive deep into SDK development, and explore features like Web Push Notifications, Service Workers, etc. 🚀 ..... Now, you're equipped with the knowledge to publish your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 This is Part 5 of our SDK development series where we get a CDN of our SDK Contents: ⚡ Getting CDN ⚡ Integrating CDN and testing SDK ⚡ Getting CDN Getting CDN ⚡ Integrating CDN and testing SDK Integrating CDN and testing SDK Step 1: Get a CDN Head over to https://www.jsdelivr.com/ , and search for your NPM package. https://www.jsdelivr.com/ Choose the default version, and copy the link. Head over to the Test Browser app, and integrate the CDN: <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="https://cdn.jsdelivr.net/npm/ts-lib-template-starter@1.0.0/dist/index.global.min.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="https://cdn.jsdelivr.net/npm/ts-lib-template-starter@1.0.0/dist/index.global.min.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> Open the file, and see the result: Step 2: Getting the Latest CDN Version Always Put @latest instead of the version to always fetch the latest CDN version @latest https://cdn.jsdelivr.net/npm/ts-lib-template-starter@latest/dist/index.global.min.js https://cdn.jsdelivr.net/npm/ts-lib-template-starter@latest/dist/index.global.min.js Sometimes, when a new version of SDK is published, jsDeliver takes a few minutes to a few days to point @latest version to the updated version. jsDeliver @latest To fix this, when you publish a new version, head over to https://www.jsdelivr.com/tools/purge , and enter the link of the CDN like: https://www.jsdelivr.com/tools/purge This will purge the cache and point @latest version to the updated version. @latest Wrapping Up: We just completed the steps to get a CDN of our SDK. Stay tuned for further parts to dive deep into SDK development, and explore features like Web Push Notifications, Service Workers, etc. 🚀 ..... Now, you're equipped with the knowledge to publish your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub GitHub LinkedIn LinkedIn LinkedIn

A 5-Year-Old Could Follow This TypeScript SDK Development Guide ~ Part 5: CDN for Browsers

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Part 1: Our First MVP Part 2: Structure and API Part 3: Making Test Apps Part 4: Publishing to npm Part 5: CDN for Browsers This is Part 4 of our SDK development series where we will publish our SDK Contents: ⚡ Creating an NPM account
⚡ Publishing to NPM, semantic versioning, and LICENSE Step 1: Creating an NPM Account Head over to https://www.npmjs.com, and create an account. Step 2: Publish In the terminal, write: npm login After following the login steps, write: npm publish This can fail due to duplicate package names or wrong configuration in package.json Your package.json should look like the following: {
  "name": "ts-lib-template-starter",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "./src/index.ts",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "tsup ./src/index.ts --watch"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/node": "^20.14.8",
    "tsup": "^8.1.0",
    "typescript": "^5.5.2"
  }
} Congrats; you just published your first SDK to NPM 🎉🥳 🚀🚀🚀 Step 3: Semantic Versioning When publishing a library, it is good to keep versioning in check. Versioning helps the developer integrate the code to get an idea of what update happened to the SDK. Furthermore, the right versioning will help package managers to update to the level as it is mentioned in their package.json. To help developers who rely on your code, we recommend starting your package version at 1.0.0 and incrementing as follows: Code status

Stage

Rule

Example version



First release

New product

Start with 1.0.0

1.0.0



Backward-compatible bug fixes

Patch release

Increment the third digit

1.0.1



Backward-compatible new features

Minor release

Increment the middle, digit and reset the last digit to zero

1.1.0



Changes that break backward compatibility

Major release

Increment the first digit and reset the middle and last digits to zero

2.0.0 Learn more about semantic versioning here: https://docs.npmjs.com/about-semantic-versioning Step 4: LICENSE Specify a license for your package so that people know how they are permitted to use it, and any restrictions you're placing on it. source: https://snyk.io/learn/open-source-licenses/ For example, this SDK is open for distribution and modifying the code so I would use MIT as LICENSE. In package.json "license": "MIT" Learn more about various types of LICENCES here: https://snyk.io/learn/open-source-licenses/ Wrapping Up: We Just completed the steps to publish our SDK. Head over to Part 5 where we will make a CDN for browsers 🚀 ..... Now, you're equipped with the knowledge to publish your own SDK. Happy coding! 🚀 That's it, folks! hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Part 1: Our First MVP Part 1: Our First MVP Part 2: Structure and API Part 2: Structure and API Part 3: Making Test Apps Part 3: Making Test Apps Part 4: Publishing to npm Part 4: Publishing to npm Part 5: CDN for Browsers Part 5: CDN for Browsers This is Part 4 of our SDK development series where we will publish our SDK Contents: ⚡ Creating an NPM account ⚡ Publishing to NPM, semantic versioning, and LICENSE ⚡ Creating an NPM account Creating an NPM account ⚡ Publishing to NPM, semantic versioning, and LICENSE Publishing to NPM, semantic versioning, and LICENSE Step 1: Creating an NPM Account Head over to https://www.npmjs.com , and create an account. https://www.npmjs.com Step 2: Publish In the terminal, write: npm login npm login After following the login steps, write: npm publish npm publish This can fail due to duplicate package names or wrong configuration in package.json package.json Your package.json should look like the following: package.json {
  "name": "ts-lib-template-starter",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "./src/index.ts",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "tsup ./src/index.ts --watch"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/node": "^20.14.8",
    "tsup": "^8.1.0",
    "typescript": "^5.5.2"
  }
} {
  "name": "ts-lib-template-starter",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "./src/index.ts",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "tsup ./src/index.ts --watch"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/node": "^20.14.8",
    "tsup": "^8.1.0",
    "typescript": "^5.5.2"
  }
} Congrats; you just published your first SDK to NPM 🎉🥳 🚀🚀🚀 Step 3: Semantic Versioning When publishing a library, it is good to keep versioning in check. Versioning helps the developer integrate the code to get an idea of what update happened to the SDK. Furthermore, the right versioning will help package managers to update to the level as it is mentioned in their package.json . package.json To help developers who rely on your code, we recommend starting your package version at 1.0.0 and incrementing as follows: 1.0.0 Code status

Stage

Rule

Example version



First release

New product

Start with 1.0.0

1.0.0



Backward-compatible bug fixes

Patch release

Increment the third digit

1.0.1



Backward-compatible new features

Minor release

Increment the middle, digit and reset the last digit to zero

1.1.0



Changes that break backward compatibility

Major release

Increment the first digit and reset the middle and last digits to zero

2.0.0 Code status

Stage

Rule

Example version First release

New product

Start with 1.0.0

1.0.0 Backward-compatible bug fixes

Patch release

Increment the third digit

1.0.1 Backward-compatible new features

Minor release

Increment the middle, digit and reset the last digit to zero

1.1.0 Changes that break backward compatibility

Major release

Increment the first digit and reset the middle and last digits to zero

2.0.0 Code status Stage Rule Example version Code status Code status Code status Stage Stage Stage Rule Rule Rule Example version Example version Example version First release New product Start with 1.0.0 1.0.0 First release First release New product New product Start with 1.0.0 Start with 1.0.0 1.0.0 1.0.0 Backward-compatible bug fixes Patch release Increment the third digit 1.0.1 Backward-compatible bug fixes Backward-compatible bug fixes Patch release Patch release Increment the third digit Increment the third digit 1.0.1 1.0.1 Backward-compatible new features Minor release Increment the middle, digit and reset the last digit to zero 1.1.0 Backward-compatible new features Backward-compatible new features Minor release Minor release Increment the middle, digit and reset the last digit to zero Increment the middle, digit and reset the last digit to zero 1.1.0 1.1.0 Changes that break backward compatibility Major release Increment the first digit and reset the middle and last digits to zero 2.0.0 Changes that break backward compatibility Changes that break backward compatibility Major release Major release Increment the first digit and reset the middle and last digits to zero Increment the first digit and reset the middle and last digits to zero 2.0.0 2.0.0 Learn more about semantic versioning here: https://docs.npmjs.com/about-semantic-versioning https://docs.npmjs.com/about-semantic-versioning Step 4: LICENSE Specify a license for your package so that people know how they are permitted to use it, and any restrictions you're placing on it. source: https://snyk.io/learn/open-source-licenses/ https://snyk.io/learn/open-source-licenses/ For example, this SDK is open for distribution and modifying the code so I would use MIT as LICENSE. In package.json package.json "license": "MIT" "license": "MIT" Learn more about various types of LICENCES here: https://snyk.io/learn/open-source-licenses/ https://snyk.io/learn/open-source-licenses/ Wrapping Up: We Just completed the steps to publish our SDK. Head over to Part 5 where we will make a CDN for browsers 🚀 ..... Now, you're equipped with the knowledge to publish your own SDK. Happy coding! 🚀 That's it, folks! hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub LinkedIn LinkedIn

A 5-Year-Old Could Follow This TypeScript SDK Development Guide ~ Part 4: Publishing to NPM

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Part 1: Our First MVP Part 2: Structure and API Part 3: Making Test Apps Part 4: Publishing to npm Part 5: CDN for Browsers This is Part 3 of our SDK development series where we will dive into creating test apps for react, browser, node, and legacy node. Contents: ⚡ Setting up tsup for different execution environments
⚡ Creating our apps Step 1: Setting Up tsup for Different Environments At the root of the project create tsup.config.ts file, and paste the following content: import { defineConfig } from "tsup";

export default defineConfig({
  clean: true,
  dts: true,
  entry: ["src/index.ts"],
  format: ["cjs", "esm", "iife"],
  minify: true,
}); clean - Clean the output directory before each build. dts - type definitions for TypeScript. entry - specifying the entry point. format - cjs for legacy, esm for newer node projects and iife for browsers. minify - minifies our code and reduces bundle size. No extra configuration is needed, as tsup will automatically look for this file and handle everything for us :) Now, exit and re-rerun the build command. npm run build You will see the following output in our dist folder. index.cjs - for CJS output index.js - for ESM index.global.js - for browsers Step 2: Create a Node App In example-apps/Node, create a index.js file. Paste the following content: import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); Now, run the file with a node in a separate terminal, and head over to the folder: node index.js You will see the output in the terminal. Step 3: Create a Legacy Node App In example-apps/Legacy-Node, create a index.cjs file, and paste the following content: const sdk = require("../../dist/index.cjs");

sdk.default.fetchUsers().then((users) => console.log(users)); Now, run the file with a node in a separate terminal, and head over to the folder: node index.cjs You will see the output in the terminal. Step 4: Create a Browser App In example-apps/Browser, create a index.html file, and paste the following content: <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="../../dist/index.global.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> Open the file in the browser, you should see the following response in the inspect element's console tab: Step 5: Create a React App Create a Link to our SDK to behave as a library for projects without publishing. npm link In example-apps, create a react app, for example, with vite: npm create vite@latest After successfully creating a react app, run the following command in the React root folder to link our SDK. npm link ts-lib In place of ts-lib, it should be your SDK/Library name in the package.json. After creating the React app, open a component file like App.jsx, and integrate SDK like the following: import sdk from "ts-lib";

console.log(await sdk.fetchUsers()); Full view: import { useState } from "react";
import reactLogo from "./assets/react.svg";
import viteLogo from "/vite.svg";
import "./App.css";
import sdk from "ts-lib";

console.log(await sdk.fetchUsers());

function App() {
  const [count, setCount] = useState(0);

  return (
    <>
      <div>
        <a href="https://vitejs.dev" target="_blank">
          <img src={viteLogo} className="logo" alt="Vite logo" />
        </a>
        <a href="https://react.dev" target="_blank">
          <img src={reactLogo} className="logo react" alt="React logo" />
        </a>
      </div>
      <h1>Vite + React</h1>
      <div className="card">
        <button onClick={() => setCount((count) => count + 1)}>
          count is {count}
        </button>
        <p>
          Edit <code>src/App.tsx</code> and save to test HMR
        </p>
      </div>
      <p className="read-the-docs">
        Click on the Vite and React logos to learn more
      </p>
    </>
  );
}

export default App; Run the react App, and head over to the console; it should look like the following: Wrapping Up: We just completed the steps to build and run our SDK in different environments. Head over to Part 4 to publish our SDK. ..... Now, you're equipped with the knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Part 1: Our First MVP Part 1: Our First MVP Part 2: Structure and API Part 2: Structure and API Part 3: Making Test Apps Part 3: Making Test Apps Part 4: Publishing to npm Part 4: Publishing to npm Part 5: CDN for Browsers Part 5: CDN for Browsers This is Part 3 of our SDK development series where we will dive into creating test apps for react, browser, node, and legacy node. SDK development series Contents: ⚡ Setting up tsup for different execution environments ⚡ Creating our apps ⚡ Setting up tsup for different execution environments Setting up tsup for different execution environments ⚡ Creating our apps Creating our apps Step 1: Setting Up tsup for Different Environments tsup At the root of the project create tsup.config.ts file, and paste the following content: tsup.config.ts import { defineConfig } from "tsup";

export default defineConfig({
  clean: true,
  dts: true,
  entry: ["src/index.ts"],
  format: ["cjs", "esm", "iife"],
  minify: true,
}); import { defineConfig } from "tsup";

export default defineConfig({
  clean: true,
  dts: true,
  entry: ["src/index.ts"],
  format: ["cjs", "esm", "iife"],
  minify: true,
}); clean - Clean the output directory before each build. clean dts - type definitions for TypeScript. dts entry - specifying the entry point. entry format - cjs for legacy, esm for newer node projects and iife for browsers. format cjs esm iife minify - minifies our code and reduces bundle size. minify No extra configuration is needed, as tsup will automatically look for this file and handle everything for us :) tsup Now, exit and re-rerun the build command. build npm run build npm run build You will see the following output in our dist folder. dist index.cjs - for CJS output index.cjs index.js - for ESM index.js index.global.js - for browsers index.global.js Step 2: Create a Node App In example-apps/Node , create a index.js file. Paste the following content: example-apps/Node index.js import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); Now, run the file with a node in a separate terminal, and head over to the folder: node index.js node index.js You will see the output in the terminal. Step 3: Create a Legacy Node App In example-apps/Legacy-Node , create a index.cjs file, and paste the following content: example-apps/Legacy-Node index.cjs const sdk = require("../../dist/index.cjs");

sdk.default.fetchUsers().then((users) => console.log(users)); const sdk = require("../../dist/index.cjs");

sdk.default.fetchUsers().then((users) => console.log(users)); Now, run the file with a node in a separate terminal, and head over to the folder: node index.cjs node index.cjs You will see the output in the terminal. Step 4: Create a Browser App In example-apps/Browser , create a index.html file, and paste the following content: example-apps/Browser index.html <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="../../dist/index.global.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> <!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="../../dist/index.global.js"></script>
  </head>
  <body>
    This is a Test HTML

    <script>
      sdk.fetchUsers().then((users) => console.log(users));
    </script>
  </body>
</html> Open the file in the browser, you should see the following response in the inspect element's console tab: Step 5: Create a React App Create a Link to our SDK to behave as a library for projects without publishing. npm link npm link In example-apps , create a react app, for example, with vite: example-apps npm create vite@latest npm create vite@latest After successfully creating a react app, run the following command in the React root folder to link our SDK. npm link ts-lib npm link ts-lib In place of ts-lib , it should be your SDK/Library name in the package.json. ts-lib After creating the React app, open a component file like App.jsx , and integrate SDK like the following: App.jsx import sdk from "ts-lib";

console.log(await sdk.fetchUsers()); import sdk from "ts-lib";

console.log(await sdk.fetchUsers()); Full view: import { useState } from "react";
import reactLogo from "./assets/react.svg";
import viteLogo from "/vite.svg";
import "./App.css";
import sdk from "ts-lib";

console.log(await sdk.fetchUsers());

function App() {
  const [count, setCount] = useState(0);

  return (
    <>
      <div>
        <a href="https://vitejs.dev" target="_blank">
          <img src={viteLogo} className="logo" alt="Vite logo" />
        </a>
        <a href="https://react.dev" target="_blank">
          <img src={reactLogo} className="logo react" alt="React logo" />
        </a>
      </div>
      <h1>Vite + React</h1>
      <div className="card">
        <button onClick={() => setCount((count) => count + 1)}>
          count is {count}
        </button>
        <p>
          Edit <code>src/App.tsx</code> and save to test HMR
        </p>
      </div>
      <p className="read-the-docs">
        Click on the Vite and React logos to learn more
      </p>
    </>
  );
}

export default App; import { useState } from "react";
import reactLogo from "./assets/react.svg";
import viteLogo from "/vite.svg";
import "./App.css";
import sdk from "ts-lib";

console.log(await sdk.fetchUsers());

function App() {
  const [count, setCount] = useState(0);

  return (
    <>
      <div>
        <a href="https://vitejs.dev" target="_blank">
          <img src={viteLogo} className="logo" alt="Vite logo" />
        </a>
        <a href="https://react.dev" target="_blank">
          <img src={reactLogo} className="logo react" alt="React logo" />
        </a>
      </div>
      <h1>Vite + React</h1>
      <div className="card">
        <button onClick={() => setCount((count) => count + 1)}>
          count is {count}
        </button>
        <p>
          Edit <code>src/App.tsx</code> and save to test HMR
        </p>
      </div>
      <p className="read-the-docs">
        Click on the Vite and React logos to learn more
      </p>
    </>
  );
}

export default App; Run the react App, and head over to the console; it should look like the following: Wrapping Up: We just completed the steps to build and run our SDK in different environments. Head over to Part 4 to publish our SDK. Part 4 ..... Now, you're equipped with the knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub LinkedIn LinkedIn

A 5-Year-Old Could Follow This TypeScript SDK Development Guide ~ Part 3: Making Test Apps

একজন 5 বছর বয়সী এই TypeScript SDK ডেভেলপমেন্ট গাইড অনুসরণ করতে পারে ~ পার্ট 3: টেস্ট অ্যাপ তৈরি করা

Diesem TypeScript SDK-Entwicklungshandbuch könnte sogar ein 5-Jähriger folgen – Teil 3: Erstellen von Test-Apps

Un niño de 5 años podría seguir esta guía de desarrollo del SDK de TypeScript ~ Parte 3: Creación de aplicaciones de prueba

Un enfant de 5 ans pourrait suivre ce guide de développement du SDK TypeScript ~ Partie 3 : Création d'applications de test

5 साल का बच्चा भी इस TypeScript SDK डेवलपमेंट गाइड को फॉलो कर सकता है ~ भाग 3: टेस्ट ऐप्स बनाना

5 歳児でも理解できる TypeScript SDK 開発ガイド ~ パート 3: テスト アプリの作成

5세 어린이도 이 TypeScript SDK 개발 가이드를 따라갈 수 있습니다 ~ 3부: 테스트 앱 만들기

Uma criança de 5 anos poderia seguir este guia de desenvolvimento do SDK TypeScript ~ Parte 3: Criando aplicativos de teste

Пятилетний ребенок может следовать этому руководству по разработке TypeScript SDK ~ Часть 3. Создание тестовых приложений

5 Yaşındaki Bir Çocuk Bu TypeScript SDK Geliştirme Kılavuzunu İzleyebilir ~ Bölüm 3: Test Uygulamaları Yapma

Trẻ 5 tuổi có thể làm theo Hướng dẫn phát triển SDK TypeScript này ~ Phần 3: Tạo ứng dụng thử nghiệm

5 岁的孩子也可以遵循这份 TypeScript SDK 开发指南〜第 3 部分：制作测试应用程序

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's Jump right in 🚀 Part 2 of our SDK development series is where we will dive into creating a folder structure and integrating an API. Heads up: any attribute or method starting from # is a private field. Private fields are truly private and are not emitted on the console log, d.ts, or elsewhere. Contents: ⚡ Creating a folder strucutre
⚡ Coding an example for fetching users from API Step 1: Creating a folder structure apis - for all external APIs models - for all our interfaces services - for business logic code index.ts - our entry point example-apps - contains our test apps for React, Browser, Node Step 2: Create a HTTP Client In src/services create a HttpClient.service.ts file and paste the following content: export class HttpClient {
  static #baseUrl: string = "https://jsonplaceholder.typicode.com";

  constructor() {}

  async get(endpoint: string) {
    try {
      const response = await fetch(`${HttpClient.#baseUrl}${endpoint}`);
      if (!response.ok) {
        throw new Error(`HTTP error! Status: ${response.status}`);
      }
      return await response.json();
    } catch (error) {
      console.error("Error fetching data:", error);
      throw error;
    }
  }
} We have created a basic HTTP Client and using jsonplaceholder as our testing API endpoint. Step 3: Creating a User Model In src/models create a User.model.ts file and paste the following content: export interface User {
  id: number;
  username: string;
  email: string;
} Step 4: Create an API to fetch Users In src/apis create a Users.api.ts file and paste the following content: import type { User } from "../models/User.model.ts";
import { HttpClient } from "../services/HttpClient.service.ts";

export class UsersAPI {
  #httpClient: HttpClient;

  constructor() {
    this.#httpClient = new HttpClient();
  }

  async getUsers(): Promise<User[]> {
    try {
      const users = await this.#httpClient.get("/users");
      return users as User[];
    } catch (error) {
      console.error("Error fetching users:", error);
      throw error;
    }
  }
} Created a basic example of fetching users from an external endpoint. Step 5: Create an Entry Point Inside src/index.ts paste the following content: import { UsersAPI } from "./apis/Users.api.ts";

class SDK {
  static #instance: SDK;
  #usersAPI: UsersAPI;

  constructor() {
    this.#usersAPI = new UsersAPI();
  }

  public static getInstance(): SDK {
    if (!SDK.#instance) {
      SDK.#instance = new SDK();
    }
    return SDK.#instance;
  }

  public fetchUsers() {
    return this.#usersAPI.getUsers();
  }
}

export default SDK.getInstance(); A basic entry point of SDK. This is a Singleton Class to have 1 existence throughout our application. Later useful when initializing with properties like API key once in application. Step 6: Build the SDK Add the following script to your package.json "build": "tsup ./src/index.ts --watch" --watch the command will watch for any changes to the directory and automatically build your SDK. Now run: npm run build Step 7: Create a test Node App In example-apps create a index.js file and paste the following content: import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); Now run the file with node: node index.js Your output should be looking like the following: Congrats 🎉🥳 🚀🚀🚀 We Just Built and Ran our first proper SDK! Wrapping Up: We Just completed the basic steps to build and run our proper SDK. Head over to Part 3, where we will integrate our first test React app, Browser app, Node app, and Legacy Node app 🚀 ..... Now, you're equipped with knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's Jump right in 🚀 Part 2 of our SDK development series is where we will dive into creating a folder structure and integrating an API. Heads up: any attribute or method starting from # is a private field. Private fields are truly private and are not emitted on the console log, d.ts , or elsewhere. # d.ts Contents: ⚡ Creating a folder strucutre ⚡ Coding an example for fetching users from API ⚡ Creating a folder strucutre Creating a folder strucutre ⚡ Coding an example for fetching users from API Coding an example for fetching users from API Step 1: Creating a folder structure apis - for all external APIs apis models - for all our interfaces models services - for business logic code services index.ts - our entry point index.ts example-apps - contains our test apps for React, Browser, Node example-apps Step 2: Create a HTTP Client In src/services create a HttpClient.service.ts file and paste the following content: src/services HttpClient.service.ts export class HttpClient {
  static #baseUrl: string = "https://jsonplaceholder.typicode.com";

  constructor() {}

  async get(endpoint: string) {
    try {
      const response = await fetch(`${HttpClient.#baseUrl}${endpoint}`);
      if (!response.ok) {
        throw new Error(`HTTP error! Status: ${response.status}`);
      }
      return await response.json();
    } catch (error) {
      console.error("Error fetching data:", error);
      throw error;
    }
  }
} export class HttpClient {
  static #baseUrl: string = "https://jsonplaceholder.typicode.com";

  constructor() {}

  async get(endpoint: string) {
    try {
      const response = await fetch(`${HttpClient.#baseUrl}${endpoint}`);
      if (!response.ok) {
        throw new Error(`HTTP error! Status: ${response.status}`);
      }
      return await response.json();
    } catch (error) {
      console.error("Error fetching data:", error);
      throw error;
    }
  }
} We have created a basic HTTP Client and using jsonplaceholder as our testing API endpoint. jsonplaceholder Step 3: Creating a User Model In src/models create a User.model.ts file and paste the following content: src/models User.model.ts export interface User {
  id: number;
  username: string;
  email: string;
} export interface User {
  id: number;
  username: string;
  email: string;
} Step 4: Create an API to fetch Users In src/apis create a Users.api.ts file and paste the following content: src/apis Users.api.ts import type { User } from "../models/User.model.ts";
import { HttpClient } from "../services/HttpClient.service.ts";

export class UsersAPI {
  #httpClient: HttpClient;

  constructor() {
    this.#httpClient = new HttpClient();
  }

  async getUsers(): Promise<User[]> {
    try {
      const users = await this.#httpClient.get("/users");
      return users as User[];
    } catch (error) {
      console.error("Error fetching users:", error);
      throw error;
    }
  }
} import type { User } from "../models/User.model.ts";
import { HttpClient } from "../services/HttpClient.service.ts";

export class UsersAPI {
  #httpClient: HttpClient;

  constructor() {
    this.#httpClient = new HttpClient();
  }

  async getUsers(): Promise<User[]> {
    try {
      const users = await this.#httpClient.get("/users");
      return users as User[];
    } catch (error) {
      console.error("Error fetching users:", error);
      throw error;
    }
  }
} Created a basic example of fetching users from an external endpoint. Step 5: Create an Entry Point Inside src/index.ts paste the following content: src/index.ts import { UsersAPI } from "./apis/Users.api.ts";

class SDK {
  static #instance: SDK;
  #usersAPI: UsersAPI;

  constructor() {
    this.#usersAPI = new UsersAPI();
  }

  public static getInstance(): SDK {
    if (!SDK.#instance) {
      SDK.#instance = new SDK();
    }
    return SDK.#instance;
  }

  public fetchUsers() {
    return this.#usersAPI.getUsers();
  }
}

export default SDK.getInstance(); import { UsersAPI } from "./apis/Users.api.ts";

class SDK {
  static #instance: SDK;
  #usersAPI: UsersAPI;

  constructor() {
    this.#usersAPI = new UsersAPI();
  }

  public static getInstance(): SDK {
    if (!SDK.#instance) {
      SDK.#instance = new SDK();
    }
    return SDK.#instance;
  }

  public fetchUsers() {
    return this.#usersAPI.getUsers();
  }
}

export default SDK.getInstance(); A basic entry point of SDK. This is a Singleton Class to have 1 existence throughout our application. Later useful when initializing with properties like API key once in application. Step 6: Build the SDK Add the following script to your package.json package.json "build": "tsup ./src/index.ts --watch" "build": "tsup ./src/index.ts --watch" --watch the command will watch for any changes to the directory and automatically build your SDK. --watch Now run: npm run build npm run build Step 7: Create a test Node App In example-apps create a index.js file and paste the following content: example-apps index.js import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); import sdk from "../../dist/index.js";

console.log(await sdk.fetchUsers()); Now run the file with node: node index.js node index.js Your output should be looking like the following: Congrats 🎉🥳 🚀🚀🚀 We Just Built and Ran our first proper SDK! Wrapping Up: We Just completed the basic steps to build and run our proper SDK. Head over to Part 3, where we will integrate our first test React app, Browser app, Node app, and Legacy Node app 🚀 ..... Now, you're equipped with knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub LinkedIn LinkedIn

TypeScript SDK Development: A 5-year-old could follow this step-by-step ~ Part 2, structure & API

Life with AI Development in the Next 500 years, According to Jail-Broken Claude Sonnet 3.5

Life in the Next 100 Years According to Jail-Broken Claude Sonnet 3.5

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Source Code: https://github.com/smyaseen/typescript-sdk-template Contents: ⚡ Some Background of SDK Development
⚡ Developing and running our first version 1️⃣ What - SDK (sometimes also known as library) serves as a plug-in in applications to derive additional features from the technology. 2️⃣ Why - SDK development with TypeScript offers reliability over a long time due to type safety and maintenance in the long run. 3️⃣ How - The fundamental steps required to build the SDK are the following: Initializing the project with the right workflow settings.
Choosing Bundler, and understanding its purpose.
Understanding ESM, CJS, IIFE UMD to run SDK on different environments.
Publishing as a library on NPM, semantic versioning, and License.
NPM for SPAs and CDN for Browsers. In Part 1, we are going to build our first basic SDK to get a basic understanding. Step 1: Initialize Project Run the following command to set the project in a new folder: npm init -y "-y" defaults to yes to all the follow-up prompts. You can change it later in the Package.json like the author, license, version, etc. Head over to package.json, and add type: module to work with the latest EcmaScript Module system (ESM). Your package.json should look like the following: {
  "name": "ts-lib",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC"
} Step 2: Install Fundamental Dev Libraries TypeScript
@types/node - to work TypeScript with NodeJS.
tsup - The simplest and fastest way to bundle your TypeScript libraries. COPY npm i typescript @types/node tsup -D Step 3: Setup tsconfig for TypeScript Settings Create a tsconfig.json file at the root of the project. COPY touch tsconfig.json Head over to the file, and paste the following configuration: {
  "compilerOptions": {
    /* Base Options: */
    "esModuleInterop": true,
    "allowImportingTsExtensions": true,
    "emitDeclarationOnly": true,
    "skipLibCheck": true,
    "target": "es2022",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "verbatimModuleSyntax": true,

    /* Strictness */
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitOverride": true,

    /* If transpiling with TypeScript: */
    "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist",

    /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"]
  },
  "exclude": ["node_modules", "dist"]
} You can hover over each property to learn more in-depth about it. The fundamental thing to understand here is: "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist", " NodeNext is the right option for authoring libraries because it prevents you from emitting ESM with module specifiers that only work in bundlers but will crash in Node.js. When writing conventional code, using common sense, and relying on high-quality dependencies, its output is usually highly compatible with bundlers and other runtimes." You can learn more about it here: https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/


sourceMap - Enables the generation of source files. These files allow debuggers and other tools to display the original TypeScript source code when working with the emitted JavaScript files. You can disable it for production.


outDir - Specify an output folder for all emitted files. /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"] declaration - Generate .d.ts files from TypeScript and JavaScript files in your project.


lib - Specify a set of bundled library declaration files that describe the target runtime environment. es2022 is for node applications like React, and dom & dom.iterable for running the library in the browser. Step 4: Write Our First Code Create a index.ts file, and write the following basic code: const add = (a: number, b: number): number => a + b;
const subtract = (a: number, b: number): number => a - b;

export { add, subtract }; Build our first code: COPY tsup ./index.ts You may now see we have a dist folder with an output file index.cjs Let's integrate and run our first SDK! Create a app.js file, and paste the following code: import { add, subtract } from "./dist/index.cjs";

console.log(add(1, 2));
console.log(subtract(2, 1)); Since we haven't published our SDK, we are directly linking with local build. Now, run our first app node app.js You should see the following output: 3
1 Congrats 🎉🥳 🚀🚀🚀 We just built and ran our first SDK! Wrapping Up: We Just completed the basic steps to build and run our first SDK. Head over to Part 2, where we will build a basic folder structure, and integrate an External API endpoint 🚀 ..... Now, you're equipped with knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's jump right in 🚀 Source Code: https://github.com/smyaseen/typescript-sdk-template https://github.com/smyaseen/typescript-sdk-template https://github.com/smyaseen/typescript-sdk-template Contents: ⚡ Some Background of SDK Development ⚡ Developing and running our first version ⚡ Some Background of SDK Development Some Background of SDK Development ⚡ Developing and running our first version Developing and running our first version 1️⃣ What - SDK (sometimes also known as library) serves as a plug-in in applications to derive additional features from the technology. 2️⃣ Why - SDK development with TypeScript offers reliability over a long time due to type safety and maintenance in the long run. 3️⃣ How - The fundamental steps required to build the SDK are the following: Initializing the project with the right workflow settings. Choosing Bundler, and understanding its purpose. Understanding ESM, CJS, IIFE UMD to run SDK on different environments. Publishing as a library on NPM, semantic versioning, and License. NPM for SPAs and CDN for Browsers. Initializing the project with the right workflow settings. Choosing Bundler, and understanding its purpose. Understanding ESM, CJS, IIFE UMD to run SDK on different environments. Publishing as a library on NPM, semantic versioning, and License. NPM for SPAs and CDN for Browsers. In Part 1, we are going to build our first basic SDK to get a basic understanding. Step 1: Initialize Project Run the following command to set the project in a new folder: npm init -y npm init -y "-y" defaults to yes to all the follow-up prompts. You can change it later in the Package.json like the author, license, version, etc. "-y" Head over to package.json , and add type: module to work with the latest EcmaScript Module system (ESM). package.json type: module Your package.json should look like the following: package.json {
  "name": "ts-lib",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC"
} {
  "name": "ts-lib",
  "version": "1.0.0",
  "description": "SDK development tutorial",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "type": "module",
  "keywords": [],
  "author": "",
  "license": "ISC"
} Step 2: Install Fundamental Dev Libraries TypeScript @types/node - to work TypeScript with NodeJS. tsup - The simplest and fastest way to bundle your TypeScript libraries. TypeScript @types/node - to work TypeScript with NodeJS. @types/node tsup - The simplest and fastest way to bundle your TypeScript libraries. tsup COPY npm i typescript @types/node tsup -D npm i typescript @types/node tsup -D Step 3: Setup tsconfig for TypeScript Settings tsconfig Create a tsconfig.json file at the root of the project. tsconfig.json COPY touch tsconfig.json touch tsconfig.json Head over to the file, and paste the following configuration: {
  "compilerOptions": {
    /* Base Options: */
    "esModuleInterop": true,
    "allowImportingTsExtensions": true,
    "emitDeclarationOnly": true,
    "skipLibCheck": true,
    "target": "es2022",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "verbatimModuleSyntax": true,

    /* Strictness */
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitOverride": true,

    /* If transpiling with TypeScript: */
    "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist",

    /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"]
  },
  "exclude": ["node_modules", "dist"]
} {
  "compilerOptions": {
    /* Base Options: */
    "esModuleInterop": true,
    "allowImportingTsExtensions": true,
    "emitDeclarationOnly": true,
    "skipLibCheck": true,
    "target": "es2022",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "verbatimModuleSyntax": true,

    /* Strictness */
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitOverride": true,

    /* If transpiling with TypeScript: */
    "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist",

    /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"]
  },
  "exclude": ["node_modules", "dist"]
} You can hover over each property to learn more in-depth about it. The fundamental thing to understand here is: "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist", "module": "NodeNext",
    "sourceMap": true,
    "outDir": "dist", " NodeNext is the right option for authoring libraries because it prevents you from emitting ESM with module specifiers that only work in bundlers but will crash in Node.js. When writing conventional code, using common sense, and relying on high-quality dependencies, its output is usually highly compatible with bundlers and other runtimes." You can learn more about it here: https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/ sourceMap - Enables the generation of source files. These files allow debuggers and other tools to display the original TypeScript source code when working with the emitted JavaScript files. You can disable it for production. outDir - Specify an output folder for all emitted files. " NodeNext is the right option for authoring libraries because it prevents you from emitting ESM with module specifiers that only work in bundlers but will crash in Node.js. When writing conventional code, using common sense, and relying on high-quality dependencies, its output is usually highly compatible with bundlers and other runtimes." You can learn more about it here: https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/ " NodeNext is the right option for authoring libraries because it prevents you from emitting ESM with module specifiers that only work in bundlers but will crash in Node.js. When writing conventional code, using common sense, and relying on high-quality dependencies, its output is usually highly compatible with bundlers and other runtimes." You can learn more about it here: https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/ NodeNext only https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/ https://blog.andrewbran.ch/is-nodenext-right-for-libraries-that-dont-target-node-js/ sourceMap - Enables the generation of source files. These files allow debuggers and other tools to display the original TypeScript source code when working with the emitted JavaScript files. You can disable it for production. sourceMap - Enables the generation of source files. These files allow debuggers and other tools to display the original TypeScript source code when working with the emitted JavaScript files. You can disable it for production. sourceMap outDir - Specify an output folder for all emitted files. outDir - Specify an output folder for all emitted files. outDir /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"] /* AND if you're building for a library: */
    "declaration": true,

    /* If your code runs in the DOM: */
    "lib": ["es2022", "dom", "dom.iterable"] declaration - Generate .d.ts files from TypeScript and JavaScript files in your project. lib - Specify a set of bundled library declaration files that describe the target runtime environment. es2022 is for node applications like React, and dom & dom.iterable for running the library in the browser. declaration - Generate .d.ts files from TypeScript and JavaScript files in your project. declaration - Generate .d.ts files from TypeScript and JavaScript files in your project. declaration lib - Specify a set of bundled library declaration files that describe the target runtime environment. es2022 is for node applications like React, and dom & dom.iterable for running the library in the browser. lib - Specify a set of bundled library declaration files that describe the target runtime environment. es2022 is for node applications like React, and dom & dom.iterable for running the library in the browser. lib es2022 dom dom.iterable Step 4: Write Our First Code Create a index.ts file, and write the following basic code: index.ts const add = (a: number, b: number): number => a + b;
const subtract = (a: number, b: number): number => a - b;

export { add, subtract }; const add = (a: number, b: number): number => a + b;
const subtract = (a: number, b: number): number => a - b;

export { add, subtract }; Build our first code: COPY tsup ./index.ts tsup ./index.ts You may now see we have a dist folder with an output file index.cjs dist index.cjs Let's integrate and run our first SDK! Create a app.js file, and paste the following code: app.js import { add, subtract } from "./dist/index.cjs";

console.log(add(1, 2));
console.log(subtract(2, 1)); import { add, subtract } from "./dist/index.cjs";

console.log(add(1, 2));
console.log(subtract(2, 1)); Since we haven't published our SDK, we are directly linking with local build. Now, run our first app node app.js node app.js You should see the following output: 3
1 3
1 Congrats 🎉🥳 🚀🚀🚀 We just built and ran our first SDK! Wrapping Up: We Just completed the basic steps to build and run our first SDK. Head over to Part 2, where we will build a basic folder structure, and integrate an External API endpoint 🚀 ..... Now, you're equipped with knowledge to build your own SDK. Happy coding! 🚀 That's it, folks! Hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub GitHub LinkedIn LinkedIn LinkedIn

TypeScript SDK Development: A 5-Year-Old Could Follow This Step-By-Step ~ Part 1: Our First MVP

TypeScript SDK ডেভেলপমেন্ট: একজন 5-বছর বয়সী এই ধাপে ধাপে অনুসরণ করতে পারে ~ পার্ট 1: আমাদের প্রথম MVP

TypeScript SDK-Entwicklung: Ein 5-Jähriger könnte dies Schritt für Schritt nachvollziehen ~ Teil 1: Unser erstes MVP

Desarrollo del SDK de TypeScript: un niño de 5 años podría seguir este paso a paso ~ Parte 1: Nuestro primer MVP

Développement du SDK TypeScript : un enfant de 5 ans pourrait suivre cette étape par étape ~ Partie 1 : Notre premier MVP

टाइपस्क्रिप्ट SDK विकास: एक 5 वर्षीय बच्चा भी इसे चरण-दर-चरण समझ सकता है ~ भाग 1: हमारा पहला MVP

TypeScript SDK 開発: 5 歳児でもステップバイステップで理解できる ~ パート 1: 最初の MVP

TypeScript SDK 개발: 5세 어린이도 따라할 수 있는 단계별 단계 ~ 1부: 첫 번째 MVP

Desenvolvimento do SDK TypeScript: uma criança de 5 anos poderia seguir este passo a passo ~ Parte 1: Nosso primeiro MVP

Разработка TypeScript SDK: 5-летний ребенок может выполнить это шаг за шагом ~ Часть 1: Наш первый MVP

TypeScript SDK Geliştirme: 5 Yaşındaki Bir Çocuk Bunu Adım Adım Takip Edebilir ~ Bölüm 1: İlk MVP'miz

Phát triển SDK TypeScript: Một đứa trẻ 5 tuổi có thể làm theo từng bước này ~ Phần 1: MVP đầu tiên của chúng tôi

TypeScript SDK 开发：5 岁小孩也能循序渐进学习~第 1 部分：我们的第一个 MVP

Now that we are only 3 years away from the iPhone’s 20th anniversary, it’s easier to imagine what it will look like for its big birthday. The past few years have helped discard a few features that seemed more plausible just a few years ago. At this point, it’s safe to assume that foldables won’t replace slab phones. That form factor will remain a niche alternative for those who don’t mind sporting a more brittle inner screen in favor of a foldable tablet experience. That won’t be the majority of users, though; we will remain using rectangular pieces of glass for the foreseeable future, including Apple’s flagship smartphone. We could still see Touch ID make a comeback, but this change is not so urgent anymore, thanks to the consistent reduction in size of the screen cutout that hosts the Face ID sensors and cameras. The introduction of smart software mitigations like the “dynamic island” also helped: originating notifications from the front-facing camera is a creative way of making the screen cutout less of a compromise and more of a positive feature. Fingerprint sensors have evolved towards under-screen ultrasonic readers, but their speed and failure rate still require significant work to rival the reliability baseline created by Touch ID in older iPhone models. So what’s left on the bingo card of features that will help make the future iPhone a momentous launch? Since we already have 5G, 120Hz displays, USB-C, and slimmer bezels on the latest iPhones, we are truly reaching peak smartphone. It’s now time for Apple to polish the experience through some critical updates. This year’s WWDC started this transition with Apple Intelligence and personalization capabilities that should have come years ago. But there is still a lot of work to get done. So here are the top 3 improvements that I would bring to the iPhone to make it a nearly perfect personal device. 1. Properly fix lens distortion on the front-facing camera One of the areas where Pixel smartphones consistently surpass even the most expensive iPhone is, embarrassingly, taking selfies. If you have an iPhone –any iPhone–, you can try this yourself. Take a selfie with the front-facing camera in vertical orientation, and then again in horizontal orientation. To see the distortion at play, you simply have to take the picture with your face near either side of the frame, a common position when you are taking a selfie with multiple people in the frame. Now compare the pictures, look at the shape and width of your face. No, you have not suddenly gained weight; what you are seeing is a normal effect on wide angle lenses. Even Apple’s recent software updates aimed at fixing lens distortion on iOS fall short. They don’t truly solve the problem and achieve natural-looking selfies. Doing the same experiment on a Pixel phone highlights the power of computational photography when leveraged effectively, producing pictures where faces on the edges of the frame are not distorted. Given that iOS can automatically detect subjects and faces at the time of taking a picture, I’m still baffled as to why Apple hasn’t yet fixed this in 2024. 2. Introduce user profiles to properly separate work and personal content Apple introduced Focus Modes with the release of iOS 15 in 2021 as an expansion of the Do Not Disturb feature. This feature offers more granular control over notifications based on user preferences. Focus Modes make it easier to define which notifications should be able to get your attention after you leave work, for example. But what if you use the same email or calendar app both for a personal account and work? What about the content itself? This is where having different user profiles shines. Creating a work profile on Android allows users to install the same app again, set it up with a work account, and control it independently from the version that provides access to the personal account. That means different widgets, different notifications, different app icon placement, etc. When Apple announced that they were making iOS more personal by allowing users to place app icons anywhere on the home screen, I thought that user profiles would also be announced. After all, user profiles open the door to another level of customization possibilities when it comes to app and notification management. But all we got was the ability to apply a color tint to all the app icons, making accessibility experts and designers (and overall, people with good taste) gasp in disbelief. 3. Provide an ultra-thin form factor with multi-day battery life If there is one improvement that is universally requested by iPhone users, generation after generation, is a better battery life. Given the hardware advancements released in the past few editions, Apple should finally focus on improving battery performance. Of course, this should not come at the expense of the phone’s thickness or size. The use of ultra-specialized Apple silicon on the iPhone lineup should help achieve the necessary low-power optimizations that finally bring us consistent multi-day battery life. Continuing with the recent iPad Pro design improvements, bringing back a thinner design on the iPhone, combined with a battery life that can last multiple days, should be the next hardware-related priority. During its first years of life, the iPhone was generally considered one of the smartphones with the best battery life. However, this claim has lost credibility over time as Apple started to cram more power-hungry tech into such a small housing. The new M4 and A17 Pro chips are trailblazers on this path. They are the first chips built on a 3-nanometer technology, they provide better performance and are more power efficient than their predecessors, while still enabling “all-day battery life”. Manufacturing techniques for sub-nanometer chips are still under research, and there are challenges due to the laws of physics. Researchers working on this technology call it a “sub-nanometer chip” or “angstrom-scale chip” (an angstrom is a unit smaller than a nanometer). Undoubtedly, Apple is on a mission to create the first sub-nanometer chip specifically designed to satisfy the always-on power needs of the iPhone. Conclusion Technology has been converging more and more over the past few years. The iOS and Android user interfaces are increasingly difficult to distinguish from each other. Navigation gestures are the same, AI capabilities are getting standardized, and even the most popular smartphones are practically mirroring each other with their latest designs. One of the advantages of breaking free from a specific ecosystem, like I did 3 years ago, is that you have more freedom when choosing your next smartphone. When a mobile OS cannot lock you in anymore, deciding your next device becomes a matter of convenience, not obligation. To maximize that convenience factor, I hope that Apple develops these improvements in the near future. Not only would it make it even easier to flip between iOS and Android as often as desired, but it would also help mitigate some of that boredom that the peak smartphone era has created. Did you like this article? Subscribe to get new posts by email. Now that we are only 3 years away from the iPhone’s 20th anniversary, it’s easier to imagine what it will look like for its big birthday. The past few years have helped discard a few features that seemed more plausible just a few years ago. 3 years away At this point, it’s safe to assume that foldables won’t replace slab phones. That form factor will remain a niche alternative for those who don’t mind sporting a more brittle inner screen in favor of a foldable tablet experience. That won’t be the majority of users, though; we will remain using rectangular pieces of glass for the foreseeable future, including Apple’s flagship smartphone. We could still see Touch ID make a comeback, but this change is not so urgent anymore, thanks to the consistent reduction in size of the screen cutout that hosts the Face ID sensors and cameras. The introduction of smart software mitigations like the “dynamic island” also helped: originating notifications from the front-facing camera is a creative way of making the screen cutout less of a compromise and more of a positive feature. Fingerprint sensors have evolved towards under-screen ultrasonic readers, but their speed and failure rate still require significant work to rival the reliability baseline created by Touch ID in older iPhone models. So what’s left on the bingo card of features that will help make the future iPhone a momentous launch? Since we already have 5G, 120Hz displays, USB-C, and slimmer bezels on the latest iPhones, we are truly reaching peak smartphone. It’s now time for Apple to polish the experience through some critical updates. This year’s WWDC started this transition with Apple Intelligence and personalization capabilities that should have come years ago. But there is still a lot of work to get done. So here are the top 3 improvements that I would bring to the iPhone to make it a nearly perfect personal device. 1. Properly fix lens distortion on the front-facing camera 1. Properly fix lens distortion on the front-facing camera One of the areas where Pixel smartphones consistently surpass even the most expensive iPhone is, embarrassingly, taking selfies. If you have an iPhone – any iPhone–, you can try this yourself. Take a selfie with the front-facing camera in vertical orientation, and then again in horizontal orientation. To see the distortion at play, you simply have to take the picture with your face near either side of the frame, a common position when you are taking a selfie with multiple people in the frame. any Now compare the pictures, look at the shape and width of your face. No, you have not suddenly gained weight; what you are seeing is a normal effect on wide angle lenses. Even Apple’s recent software updates aimed at fixing lens distortion on iOS fall short. They don’t truly solve the problem and achieve natural-looking selfies. Doing the same experiment on a Pixel phone highlights the power of computational photography when leveraged effectively, producing pictures where faces on the edges of the frame are not distorted. Given that iOS can automatically detect subjects and faces at the time of taking a picture, I’m still baffled as to why Apple hasn’t yet fixed this in 2024. 2. Introduce user profiles to properly separate work and personal content 2. Introduce user profiles to properly separate work and personal content Apple introduced Focus Modes with the release of iOS 15 in 2021 as an expansion of the Do Not Disturb feature. This feature offers more granular control over notifications based on user preferences. Focus Modes make it easier to define which notifications should be able to get your attention after you leave work, for example. But what if you use the same email or calendar app both for a personal account and work? What about the content itself? This is where having different user profiles shines. Creating a work profile on Android allows users to install the same app again, set it up with a work account, and control it independently from the version that provides access to the personal account. That means different widgets, different notifications, different app icon placement, etc. When Apple announced that they were making iOS more personal by allowing users to place app icons anywhere on the home screen, I thought that user profiles would also be announced. After all, user profiles open the door to another level of customization possibilities when it comes to app and notification management. But all we got was the ability to apply a color tint to all the app icons, making accessibility experts and designers (and overall, people with good taste) gasp in disbelief. 3. Provide an ultra-thin form factor with multi-day battery life 3. Provide an ultra-thin form factor with multi-day battery life If there is one improvement that is universally requested by iPhone users, generation after generation, is a better battery life. Given the hardware advancements released in the past few editions, Apple should finally focus on improving battery performance. Of course, this should not come at the expense of the phone’s thickness or size. The use of ultra-specialized Apple silicon on the iPhone lineup should help achieve the necessary low-power optimizations that finally bring us consistent multi-day battery life. Continuing with the recent iPad Pro design improvements, bringing back a thinner design on the iPhone, combined with a battery life that can last multiple days, should be the next hardware-related priority. During its first years of life, the iPhone was generally considered one of the smartphones with the best battery life. However, this claim has lost credibility over time as Apple started to cram more power-hungry tech into such a small housing. The new M4 and A17 Pro chips are trailblazers on this path. They are the first chips built on a 3-nanometer technology, they provide better performance and are more power efficient than their predecessors, while still enabling “all-day battery life”. Manufacturing techniques for sub-nanometer chips are still under research, and there are challenges due to the laws of physics. Researchers working on this technology call it a “sub-nanometer chip” or “angstrom-scale chip” (an angstrom is a unit smaller than a nanometer). Undoubtedly, Apple is on a mission to create the first sub-nanometer chip specifically designed to satisfy the always-on power needs of the iPhone. Conclusion Conclusion Technology has been converging more and more over the past few years. The iOS and Android user interfaces are increasingly difficult to distinguish from each other. Navigation gestures are the same, AI capabilities are getting standardized, and even the most popular smartphones are practically mirroring each other with their latest designs. One of the advantages of breaking free from a specific ecosystem, like I did 3 years ago , is that you have more freedom when choosing your next smartphone. When a mobile OS cannot lock you in anymore, deciding your next device becomes a matter of convenience, not obligation. like I did 3 years ago To maximize that convenience factor, I hope that Apple develops these improvements in the near future. Not only would it make it even easier to flip between iOS and Android as often as desired, but it would also help mitigate some of that boredom that the peak smartphone era has created. Did you like this article? Subscribe to get new posts by email. Did you like this article? Subscribe to get new posts by email. Subscribe

The Future of iPhone: 3 Features Apple Needs To Implement After 20 Years

**HONG KONG, HongKong, July 4th, 2024/Chainwire/--**ASIC MARKETPLACE is celebrating 3 remarkable years of leading the industry as the most reliable Asic sourcing platform, serving robust ASIC Miners across the world, marking phenomenal achievement and growth in the mining landscape. ASIC marketplace has been in the industry since 2021, where it has performed as a pioneer in reselling the 12800+ ASIC Mining Hardware successfully to date across 80+ countries marketplace calls itself a successful and happy family of 4300+ customers globally due to the contributions it has made to deliver groundbreaking ASIC Miners to its customers at their doorstep. The company is known well for its innovative and economical range of ASIC Miners curated for every kind of consumer, its commitment to delivering the best, and its vision for elevating the mining experience for everyone who is or wants to be an integral part of the ASIC Mining industry. ASIC marketplace has reliably set a pertinent benchmark in the industry by collaborating with renowned players of the industry manufacturers to deliver high-quality products to help the miners reach their goals. Asic Marketplace constantly dedicates its success and extends warm thanks to its team members and customers for the unwavering support that they provided them over these three excellent years. The mining industry evolves each day, and new advancements are being introduced every time, which demand new innovative mining machines. Asic Marketplace stands firm as a pillar here that makes it possible for novices as well as professionals to cater for their mining needs, which speaks volumes about the work they have done over the years. The three-year milestone is a testament to the success of their collaboration with hi-tech industry leaders and manufacturers, which solidifies their position as a winning and highly recognized eCommerce platform. For more information, users can contact Asic Marketplace using the details mentioned below. About ASIC Marketplace ASIC Marketplace is a leading platform dedicated to providing a wide range of ASIC mining hardware. Founded in 2021, the company has quickly become a trusted name in the industry, known for its commitment to quality and customer satisfaction. With a presence in over 80 countries and a customer base exceeding 4,300 clients, ASIC Marketplace offers innovative and economical mining solutions to meet the diverse needs of the global mining community. Website: https://asicmarketplace.com/ Contact Manager Rain Lee Asic Marketplace rain@asicmarketplace.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here. **HONG KONG, HongKong, July 4th, 2024/Chainwire/--**ASIC MARKETPLACE is celebrating 3 remarkable years of leading the industry as the most reliable Asic sourcing platform, serving robust ASIC Miners across the world, marking phenomenal achievement and growth in the mining landscape. ASIC marketplace has been in the industry since 2021, where it has performed as a pioneer in reselling the 12800+ ASIC Mining Hardware successfully to date across 80+ countries marketplace calls itself a successful and happy family of 4300+ customers globally due to the contributions it has made to deliver groundbreaking ASIC Miners to its customers at their doorstep. The company is known well for its innovative and economical range of ASIC Miners curated for every kind of consumer, its commitment to delivering the best, and its vision for elevating the mining experience for everyone who is or wants to be an integral part of the ASIC Mining industry. ASIC Mining ASIC Mining ASIC marketplace has reliably set a pertinent benchmark in the industry by collaborating with renowned players of the industry manufacturers to deliver high-quality products to help the miners reach their goals. Asic Marketplace constantly dedicates its success and extends warm thanks to its team members and customers for the unwavering support that they provided them over these three excellent years. The mining industry evolves each day, and new advancements are being introduced every time, which demand new innovative mining machines. Asic Marketplace stands firm as a pillar here that makes it possible for novices as well as professionals to cater for their mining needs, which speaks volumes about the work they have done over the years. The three-year milestone is a testament to the success of their collaboration with hi-tech industry leaders and manufacturers, which solidifies their position as a winning and highly recognized eCommerce platform. For more information, users can contact Asic Marketplace using the details mentioned below. About ASIC Marketplace ASIC Marketplace is a leading platform dedicated to providing a wide range of ASIC mining hardware. Founded in 2021, the company has quickly become a trusted name in the industry, known for its commitment to quality and customer satisfaction. ASIC Marketplace ASIC Marketplace With a presence in over 80 countries and a customer base exceeding 4,300 clients, ASIC Marketplace offers innovative and economical mining solutions to meet the diverse needs of the global mining community. Website: https://asicmarketplace.com/ https://asicmarketplace.com/ https://asicmarketplace.com/ Contact Manager Rain Lee Asic Marketplace rain@asicmarketplace.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here. This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here . here here

Asic Marketplace Celebrates 3 Remarkable Years Of Excellence In The Mining Industry

Stories, News & Mentions about YERA

Yera’s Stories on HackerNoon