Poddin

poddin

The Corner Pub.

I have been podcasting for a year now between and , and I've learned a few things about audio. I'm in no way an audio expert yet and my background isn't in audio engineering or production. But, one day in 2020 I bought a mic and started learning lessons the hard way - by doing, f*cking up, and improving. The Art Hustlers' Studio The HackerNoon Podcast Over the past year, I've made audio mistakes and it has been fabulous for and growth. On the very first podcast episode I recorded, I had my mic muted for the first half of the episode. On an episode I recorded with an in-person guest, the audio was horrifying because I didn't know how to position the mic. With this slogging thread and story, I hope you can learn from some of my mistakes by adjusting to the optimal settings for your Yeti Blue mic. many my career The Yeti Blue Mic There are a few nobs on the Yeti Blue mic. The first is the . As part of my pre-recording checklist, I always make sure I can see a solid red light on that mute button, which indicates the mic is on and not muted. If you're light is flashing, you won't be recording audio, my friend. mute button The next nob is the . As a podcaster who records with guests, this dial is pretty much just for show. Apparently, you can plug your headphones directly into the mic - I've never needed to do this. volume dial On the backside of the mic, I have the . Gain refers to the level of sound output for the mic. If the gain is too high, you'll get clipped. If the gain is too low, you won't hear anything; the gain dial is very sensitive. To give you some context, on one of the latest recordings of The HackerNoon Podcast, one of the mic's gain was set at 3 o'clock and that was way too high. Mine is set at 8 o'clock, but I also have a vocal booth surrounding my mic which helps. Try setting your dial to 9 o'clock to start. In general, I'd say it's better to err on the side of quiet than loud because it can mostly be adjusted in post (unless it's TOO quiet). gain nob Below the gain nob is the . This dial changes the type of recording pattern your mic will use. There are four kinds of patterns: cardioid, stereo, omnidirectional, and bidirectional. For podcasting, you should be using the cardioid setting which is the one that looks like a little butt. This is optimized so that whatever is directly in front of the mic (in this case you) will be recorded. If you were recording with a guest in person and with only one mic, you'd want to change to omnidirectional or bidirectional. pattern nob Image source One other important thing to remember about using the Blue Yeti mic is where to speak into the mic. Most people want to point the tip of the mic towards their mouth, but you should actually be keeping the mic up and down and talking into the side of it. You also don't want to be too close and talking directly into the mic itself. It's better to talk at least a foot back and turn up the gain if you need to. Image source This Slogging thread by Alex Cobb, Amy, David, Guy and Linh occurred in hackernoon's official #podcast channel, and has been edited for readability. Alex Cobb Jul 8, 2021, 2:45 PM What's everyone setting his or her gain to for the TWOPI recordings? Also, is everyone making sure to keep audio rolling throughout and not cutting it off partway through? 🤔 1 Alex Cobb Jul 8, 2021, 2:48 PM Because someone may have clipped a bit...the entire episode Amy Jul 8, 2021, 3:02 PM Alex Cobb Jul 8, 2021, 3:04 PM Yours looks good! I like 9 o'clock, but it sounds great. That sounds insulating is doing numbers. 🔥 1 Alex Cobb Jul 8, 2021, 3:05 PM Sound* Amy Jul 8, 2021, 3:37 PM David I believe you are the culprit in question 😂 Alex Cobb Jul 8, 2021, 3:37 PM Not pointing any fingers or naming any names, but it's not Amy, and the gain problem specifically isn't Guy. David Jul 8, 2021, 3:55 PM ha its probably me, I attached a mic for the first time. its also a yetti. it worked fine via restream in this first recording and then twopi and storm podcast yesterday was second and third time using it. https://twitter.com/productschool/status/1412501856870449152 David Jul 8, 2021, 3:55 PM with this computer. Amy Jul 8, 2021, 3:56 PM you probs just need to put your gain to 9'oclock. “clipping” means it was too loud so you went over the audio threshold for appropriate volume :savage-smiling-with-tear: 😂 1 :savage-joy: 1 :savage-smiling-with-tear: 1 Alex Cobb Jul 8, 2021, 3:57 PM Audio expert over here^ :face_with_monocle: 😂 1 Guy Jul 8, 2021, 3:57 PM Who’s gain? But glad my $30 5 year-old mic isn’t causing too many issues hehe Alex Cobb Jul 8, 2021, 3:58 PM Your issue was muting your audio periodically and inadvertently pausing the recording. Alex Cobb Jul 8, 2021, 3:59 PM So, it's not a competition, but Amy wins. 🍾 2 🏆 2 David Jul 8, 2021, 3:59 PM Is Storm's also off? Are those two recordings salvagable/publishable? podcast ✅ 1 David Jul 8, 2021, 3:59 PM Gain was at 3 oclock, just moved to 9 oclock now Guy Jul 8, 2021, 4:00 PM Does muting on zoom affect the recording (even when I’m not speaking)? I HAVE A SQUEAKY CHAIR 😂 1 Alex Cobb Jul 8, 2021, 4:00 PM Yup. It's an abysmal system. We truly do live in a society. Do they have WD-40 over there? Alex Cobb Jul 8, 2021, 4:01 PM Can we hear a test of 9 o'clock? Idk if you can send it over the slack. Guy Jul 8, 2021, 4:02 PM I’ve been meaning to give it a good spray-down for ages, but cheers for letting me know about the zoom muting thing! Alex Cobb Jul 8, 2021, 4:03 PM Yeah, it's something no one else seems to realise and I only found out about by reading the podcast recording guidelines. Terrible system from Zoom. Only way around it would be recording a separate track as well. No worries, tho, mate. Took care of it. Cheers. 🙌 2 Amy Jul 8, 2021, 4:18 PM David you also gotta change the bottom dial to the butt looking icon loooool David Jul 8, 2021, 7:32 PM https://www.youtube.com/watch?v=G4PvTrTp7Tc :man-facepalming: 1 😂 1 Linh Jul 8, 2021, 9:25 PM omg what’s going on??? i don’t understand anything =))) Alex Cobb Jul 8, 2021, 9:28 PM It's also called cardioid, but that's SO much less fun to say. Linh Jul 8, 2021, 9:30 PM so i’m planning to use the yeti mic with the dongle as mentioned at the end of the twopi episode, awhat now? do i have to know anything about zoom setting or what have you? Alex Cobb Jul 8, 2021, 9:36 PM I'd say don't mute your Zoom call under any circumstances. I THINK you can mute the mic If you have to. Linh Jul 8, 2021, 9:37 PM omg that’s news for me. ok. how does one mute the mic though 🙈 Alex Cobb Jul 8, 2021, 9:37 PM Should be a button, depending on the model. Amy's doesn't seem to have one. My model has a little button right in the middle. Amy Jul 8, 2021, 9:39 PM Oh my mute button is on the other side Amy Jul 8, 2021, 9:39 PM Have 10/10 recorded entire episodes with the mic muted in the past SOOO That's it, everyone - thanks for reading! I hope this helps you avoid some of the same audio mistakes I was making. If you want to check out my podcasts, you can listen to The Art Hustlers' Studio or The HackerNoon Podcast on Apple Podcasts, Spotify, or wherever you get your podcasts. In the meantime, I'll be podding hard.

How to Adjust the Blue Yeti Microphone Settings For Podcasting

Cómo ajustar la configuración del micrófono Blue Yeti para podcasting

Mr. Slope Manages Matters Very Cleverly at Puddingdale

The Story Girl by L. M. Montgomery, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . THE PROOF OF THE PUDDING CHAPTER XVII. THE PROOF OF THE PUDDING Felicity was cumbered with many cares the next morning. For one thing, the whole house must be put in apple pie order; and for another, an elaborate supper must be prepared for the expected return of the travellers that night. Felicity devoted her whole attention to this, and left the secondary preparation of the regular meals to Cecily and the Story Girl. It was agreed that the latter was to make a cornmeal pudding for dinner. In spite of her disaster with the bread, the Story Girl had been taking cooking lessons from Felicity all the week, and getting on tolerably well, although, mindful of her former mistake, she never ventured on anything without Felicity’s approval. But Felicity had no time to oversee her this morning. “You must attend to the pudding yourself,” she said. “The recipe’s so plain and simple even you can’t go astray, and if there’s anything you don’t understand you can ask me. But don’t bother me if you can help it.” The Story Girl did not bother her once. The pudding was concocted and baked, as the Story Girl proudly informed us when we came to the dinner-table, all on her own hook. She was very proud of it; and certainly as far as appearance went it justified her triumph. The slices were smooth and golden; and, smothered in the luscious maple sugar sauce which Cecily had compounded, were very fair to view. Nevertheless, although none of us, not even Uncle Roger or Felicity, said a word at the time, for fear of hurting the Story Girl’s feelings, the pudding did not taste exactly as it should. It was tough—decidedly tough—and lacked the richness of flavour which was customary in Aunt Janet’s cornmeal puddings. If it had not been for the abundant supply of sauce it would have been very dry eating indeed. Eaten it was, however, to the last crumb. If it were not just what a cornmeal pudding might be, the rest of the bill of fare had been extra good and our appetites matched it. “I wish I was twins so’s I could eat more,” said Dan, when he simply had to stop. “What good would being twins do you?” asked Peter. “People who squint can’t eat any more than people who don’t squint, can they?” We could not see any connection between Peter’s two questions. “What has squinting got to do with twins?” asked Dan. “Why, twins are just people that squint, aren’t they?” said Peter. We thought he was trying to be funny, until we found out that he was quite in earnest. Then we laughed until Peter got sulky. “I don’t care,” he said. “How’s a fellow to know? Tommy and Adam Cowan, over at Markdale, are twins; and they’re both cross-eyed. So I s’posed that was what being twins meant. It’s all very fine for you fellows to laugh. I never went to school half as much as you did; and you was brought up in Toronto, too. If you’d worked out ever since you was seven, and just got to school in the winter, there’d be lots of things you wouldn’t know, either.” “Never mind, Peter,” said Cecily. “You know lots of things they don’t.” But Peter was not to be conciliated, and took himself off in high dudgeon. To be laughed at before Felicity—to be laughed at BY Felicity—was something he could not endure. Let Cecily and the Story Girl cackle all they wanted to, and let those stuck-up Toronto boys grin like chessy-cats; but when Felicity laughed at him the iron entered into Peter’s soul. If the Story Girl laughed at Peter the mills of the gods ground out his revenge for him in mid-afternoon. Felicity, having used up all the available cooking materials in the house, had to stop perforce; and she now determined to stuff two new pincushions she had been making for her room. We heard her rummaging in the pantry as we sat on the cool, spruce-shadowed cellar door outside, where Uncle Roger was showing us how to make elderberry pop-guns. Presently she came out, frowning. “Cecily, do you know where mother put the sawdust she emptied out of that old beaded pincushion of Grandmother King’s, after she had sifted the needles out of it? I thought it was in the tin box.” “So it is,” said Cecily. “It isn’t. There isn’t a speck of sawdust in that box.” The Story Girl’s face wore a quite indescribable expression, compound of horror and shame. She need not have confessed. If she had but held her tongue the mystery of the sawdust’s disappearance might have forever remained a mystery. She WOULD have held her tongue, as she afterwards confided to me, if it had not been for a horrible fear which flashed into her mind that possibly sawdust puddings were not healthy for people to eat—especially if there might be needles in them—and that if any mischief had been done in that direction it was her duty to undo it if possible at any cost of ridicule to herself. “Oh, Felicity,” she said, her voice expressing a very anguish of humiliation, “I—I—thought that stuff in the box was cornmeal and used it to make the pudding.” Felicity and Cecily stared blankly at the Story Girl. We boys began to laugh, but were checked midway by Uncle Roger. He was rocking himself back and forth, with his hand pressed against his stomach. “Oh,” he groaned, “I’ve been wondering what these sharp pains I’ve been feeling ever since dinner meant. I know now. I must have swallowed a needle—several needles, perhaps. I’m done for!” The poor Story Girl went very white. “Oh, Uncle Roger, could it be possible? You COULDN’T have swallowed a needle without knowing it. It would have stuck in your tongue or teeth.” “I didn’t chew the pudding,” groaned Uncle Roger. “It was too tough—I just swallowed the chunks whole.” He groaned and twisted and doubled himself up. But he overdid it. He was not as good an actor as the Story Girl. Felicity looked scornfully at him. “Uncle Roger, you are not one bit sick,” she said deliberately. “You are just putting on.” “Felicity, if I die from the effects of eating sawdust pudding, flavoured with needles, you’ll be sorry you ever said such a thing to your poor old uncle,” said Uncle Roger reproachfully. “Even if there were no needles in it, sixty-year-old sawdust can’t be good for my tummy. I daresay it wasn’t even clean.” “Well, you know every one has to eat a peck of dirt in his life,” giggled Felicity. “But nobody has to eat it all at once,” retorted Uncle Roger, with another groan. “Oh, Sara Stanley, it’s a thankful man I am that your Aunt Olivia is to be home to-night. You’d have me kilt entirely by another day. I believe you did it on purpose to have a story to tell.” Uncle Roger hobbled off to the barn, still holding on to his stomach. “Do you think he really feels sick?” asked the Story Girl anxiously. “No, I don’t,” said Felicity. “You needn’t worry over him. There’s nothing the matter with him. I don’t believe there were any needles in that sawdust. Mother sifted it very carefully.” “I know a story about a man whose son swallowed a mouse,” said the Story Girl, who would probably have known a story and tried to tell it if she were being led to the stake. “And he ran and wakened up a very tired doctor just as he had got to sleep. “‘Oh, doctor, my son has swallowed a mouse,’ he cried. ‘What shall I do?’ “‘Tell him to swallow a cat,’ roared the poor doctor, and slammed his door. “Now, if Uncle Roger has swallowed any needles, maybe it would make it all right if he swallowed a pincushion.” We all laughed. But Felicity soon grew sober. “It seems awful to think of eating a sawdust pudding. How on earth did you make such a mistake?” “It looked just like cornmeal,” said the Story Girl, going from white to red in her shame. “Well, I’m going to give up trying to cook, and stick to things I can do. And if ever one of you mentions sawdust pudding to me I’ll never tell you another story as long as I live.” The threat was effectual. Never did we mention that unholy pudding. But the Story Girl could not so impose silence on the grown-ups, especially Uncle Roger. He tormented her for the rest of the summer. Never a breakfast did he sit down to, without gravely inquiring if they were sure there was no sawdust in the porridge. Not a tweak of rheumatism did he feel but he vowed it was due to a needle, travelling about his body. And Aunt Olivia was warned to label all the pincushions in the house. “Contents, sawdust; not intended for puddings.” About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. L. M. Montgomery (2004). The Story Girl. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/5342/pg5342-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html .

THE PROOF OF THE PUDDING

The cryptocurrency industry has never shied away from making big claims. And nor should it; blockchain technology is truly revolutionary. Decentralized cryptocurrencies and stablecoins offer an alternative to their hyperinflating local currency, an alternative that cannot be overnight. Smart contracts bring equitable agreements to the billions of people living in countries that lack fair and stable judicial systems. hundreds of millions of people seized by a bankrupt government Yet this promise of a fairer and freer world is overshadowed by the hype and scandal that has plagued the industry in recent times. As CEO of , a blockchain security firm, I have closer contact than most with the hundreds of hacks and scams that drain billions of dollars of value from Web3 every year. While there are many incredible projects out there that take security seriously and will go to any lengths necessary to protect their customers' funds while delivering a cutting-edge service, it's disappointing to see more than alone. CertiK $3.7 billion lost in 2022 And that's just the on-chain figure, it doesn't count the many billions more currently locked up in bankruptcy proceedings after the collapse of a number of major centralized crypto firms and exchanges. FTX was the major story of the latter quarter of last year. Amid all the allegations of fraud and complete lack of due diligence, the fact remains that users were ultimately unable to access the funds they had deposited when they needed them, and many livelihoods were destroyed. For an industry that prides itself on trustlessness and decentralization, this is not a good look. Crypto firms need to take a good hard look at the lessons that must be learned from FTX's collapse. It's the only way the industry as a whole will progress in the right direction and deliver on its real promise. Centralized exchanges play an important role in the broader crypto landscape. They are one of the easiest ways for users to deposit and withdraw fiat currency. They allow for the low-fee trading of thousands of assets, which is invaluable to users who may not have the capital to make trading on-chain an economical choice. Yet there remains a fundamental contradiction between and . The solution is not to abolish one in favor of the other, it's for centralized platforms to learn what they can from decentralized platforms, adopting crypto-native improvements wherever possible. centralized exchanges decentralized assets and applications This is the right thing to do for both a centralized platform's users and its business. FTX users who were burned by the exchange's lack of transparency are unlikely to trust their assets to another exchange that doesn't go above and beyond to prove to its customers that its solvent. And more FTX-like collapses will drag the industry down further. Anyone who believes in the power of blockchain technology to change the world for the better has a duty (and financial interest) to raise the level of security and transparency across the entire industry. Enter Proof of Reserves One example of a crypto-native solution that can (and should) be adopted by centralized crypto firms is Proof of Reserves. The term Proof of Reserves refers to a number of methods by which cryptocurrency exchanges and other organizations can demonstrate their solvency and show that they do actually hold the assets they claim to have in reserve. Cryptographic Proof of Reserves is a secure and user-verifiable way of proving that an exchange controls the assets they say they do. can be used to prove the existence of a set of customer deposits without revealing the actual balances or details of individual customer accounts. Merkle trees A Merkle tree is a data structure that is often used in proof of reserves to demonstrate the authenticity and integrity of a set of transactions. A Merkle tree is a tree-like structure that is created by breaking down a set of transactions (including user deposits) into smaller hash values, which are then combined and hashed again in a recursive manner. The root of the Merkle tree is the final hash value, which represents the combined hash of all the transactions in the set. This root hash can be published by the exchange, allowing users to verify that their account balance is included in the set. This form of Proof of Reserves is far superior to quarterly statements or audits that merely attest to an exchange's reserves. With cryptographic Proof of Reserves, you don't need to trust anyone, you can verify, by yourself, that your deposits have been included in the Merkle tree. One Small Step for Exchanges, One Giant Leap for Crypto The adoption of cryptographic Proof of Reserves is an easily-achievable step for exchanges that will have broad significance for the wider industry. It will be proof that we are learning the lessons that need to be learned and making the kind of fraud that impacted millions of FTX users much more difficult to conceal. It's also the sort of proactive self-regulation that sends a powerful message to the non-crypto world. Regulation is a tricky topic, but taking serious measures to protect users can only earn the industry goodwill. And who better to regulate the industry than those who understand it best and can build crypto-native tools themselves? If it's not us, that job falls to outsiders who will not view our failure to self-regulate kindly. Cryptographic Proof of Reserves does not compromise on any of the foundational ethics of crypto. In fact, it helps preserve them, by calling out those organizations that trade off the name of crypto without living up to its ideals. The adoption of cryptographic Proof of Reserves is a test for the industry, and it's one that we must pass in order to really build the future we all believe in. Lead image generated with stable diffusion.

The Proof is in the Pudding: Crypto's Existential Test

Day 24: Designing Forms and Handling User Input Validation 📋 Let's go to the basics today with by creating forms and handling user input in SwiftUI. Forms are a core part of many apps for collecting data from users. Let’s jump in! Code SwiftUI provides the Formcontainer, making it easy to create user-friendly input forms. import SwiftUI

struct UserFormView: View {
    @State private var username = ""
    @State private var email = ""
    @State private var password = ""
    @State private var errorMessage = ""

    var body: some View {
        Form {
            // Username Input
            Section(header: Text("Username")) {
                TextField("Enter your username", text: $username)
                    .autocapitalization(.none)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Email Input
            Section(header: Text("Email")) {
                TextField("Enter your email", text: $email)
                    .autocapitalization(.none)
                    .keyboardType(.emailAddress)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Password Input
            Section(header: Text("Password")) {
                SecureField("Enter your password", text: $password)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Error Message
            if !errorMessage.isEmpty {
                Text(errorMessage)
                    .foregroundColor(.red)
            }

            // Submit Button
            Button(action: {
                validateForm()
            }) {
                Text("Submit")
                    .frame(maxWidth: .infinity)
                    .padding()
                    .background(Color.blue)
                    .foregroundColor(.white)
                    .cornerRadius(8)
            }
        }
        .navigationTitle("User Form")
    }

    // Step 3: Validate the form inputs
    func validateForm() {
        if username.isEmpty || email.isEmpty || password.isEmpty {
            errorMessage = "All fields are required!"
        } else if !email.contains("@") {
            errorMessage = "Invalid email address!"
        } else if password.count < 6 {
            errorMessage = "Password must be at least 6 characters!"
        } else {
            errorMessage = ""
            // Handle successful form submission (e.g., save data)
        }
    }
} The full series is available on my profile and the components can also be found at shipios.app/components. Happy Coding! Day 24: Designing Forms and Handling User Input Validation 📋 Day 24: Designing Forms and Handling User Input Validation 📋 Let's go to the basics today with by creating forms and handling user input in SwiftUI . Forms are a core part of many apps for collecting data from users. SwiftUI Let’s jump in! Code SwiftUI provides the Form container, making it easy to create user-friendly input forms. SwiftUI Form import SwiftUI

struct UserFormView: View {
    @State private var username = ""
    @State private var email = ""
    @State private var password = ""
    @State private var errorMessage = ""

    var body: some View {
        Form {
            // Username Input
            Section(header: Text("Username")) {
                TextField("Enter your username", text: $username)
                    .autocapitalization(.none)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Email Input
            Section(header: Text("Email")) {
                TextField("Enter your email", text: $email)
                    .autocapitalization(.none)
                    .keyboardType(.emailAddress)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Password Input
            Section(header: Text("Password")) {
                SecureField("Enter your password", text: $password)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Error Message
            if !errorMessage.isEmpty {
                Text(errorMessage)
                    .foregroundColor(.red)
            }

            // Submit Button
            Button(action: {
                validateForm()
            }) {
                Text("Submit")
                    .frame(maxWidth: .infinity)
                    .padding()
                    .background(Color.blue)
                    .foregroundColor(.white)
                    .cornerRadius(8)
            }
        }
        .navigationTitle("User Form")
    }

    // Step 3: Validate the form inputs
    func validateForm() {
        if username.isEmpty || email.isEmpty || password.isEmpty {
            errorMessage = "All fields are required!"
        } else if !email.contains("@") {
            errorMessage = "Invalid email address!"
        } else if password.count < 6 {
            errorMessage = "Password must be at least 6 characters!"
        } else {
            errorMessage = ""
            // Handle successful form submission (e.g., save data)
        }
    }
} import SwiftUI

struct UserFormView: View {
    @State private var username = ""
    @State private var email = ""
    @State private var password = ""
    @State private var errorMessage = ""

    var body: some View {
        Form {
            // Username Input
            Section(header: Text("Username")) {
                TextField("Enter your username", text: $username)
                    .autocapitalization(.none)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Email Input
            Section(header: Text("Email")) {
                TextField("Enter your email", text: $email)
                    .autocapitalization(.none)
                    .keyboardType(.emailAddress)
                    .disableAutocorrection(true)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Password Input
            Section(header: Text("Password")) {
                SecureField("Enter your password", text: $password)
                    .textFieldStyle(RoundedBorderTextFieldStyle())
            }

            // Error Message
            if !errorMessage.isEmpty {
                Text(errorMessage)
                    .foregroundColor(.red)
            }

            // Submit Button
            Button(action: {
                validateForm()
            }) {
                Text("Submit")
                    .frame(maxWidth: .infinity)
                    .padding()
                    .background(Color.blue)
                    .foregroundColor(.white)
                    .cornerRadius(8)
            }
        }
        .navigationTitle("User Form")
    }

    // Step 3: Validate the form inputs
    func validateForm() {
        if username.isEmpty || email.isEmpty || password.isEmpty {
            errorMessage = "All fields are required!"
        } else if !email.contains("@") {
            errorMessage = "Invalid email address!"
        } else if password.count < 6 {
            errorMessage = "Password must be at least 6 characters!"
        } else {
            errorMessage = ""
            // Handle successful form submission (e.g., save data)
        }
    }
} The full series is available on my profile and the components can also be found at shipios.app/components . shipios.app/components shipios.app/components Happy Coding! Happy Coding!

Forms and Input Handling in iOS 18 - #30DaysOfSwift

Day 23: AVKit Integration – Playing Videos and Media in SwiftUI 🎬 Today, we’ll explore how to integrate AVKit into your SwiftUI project. AVKit is the framework that lets you play videos and audio seamlessly with built-in controls. Comments for Customization: player.play(): This starts video playback.
cornerRadius(10): This rounds the corners of the video view, making it visually appealing.
frame(height: 300): The video player is confined to a specific height, ensuring a clean layout. Here's the code for the implementation shown: import AVKit
import SwiftUI

struct VideoPlayerView: View {
    private var player = AVPlayer(url: URL(string: "https://www.example.com/samplevideo.mp4")!)

    var body: some View {
        VStack {
            VideoPlayer(player: player)
                .frame(height: 300)
                .cornerRadius(10)

            HStack {
                Button("Play Video") {
                    player.play()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.blue)
                .cornerRadius(8)

                Button("Pause Video") {
                    player.pause()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.red)
                .cornerRadius(8)
            }
            .padding(.top, 20)
        }
        .padding()
    }
}

struct ContentView: View {
    var body: some View {
        VStack {
            Text("Welcome to Video Player")
                .font(.largeTitle)
                .padding()

            VideoPlayerView()
        }
    }
} The full series is available on my profile and the components can also be found at shipios.app/components. Happy Coding! 🎨 Day 23: AVKit Integration – Playing Videos and Media in SwiftUI 🎬 Day 23: AVKit Integration – Playing Videos and Media in SwiftUI 🎬 Today, we’ll explore how to integrate AVKit into your SwiftUI project. AVKit is the framework that lets you play videos and audio seamlessly with built-in controls. AVKit SwiftUI Comments for Customization: Comments for Customization: player.play(): This starts video playback. cornerRadius(10): This rounds the corners of the video view, making it visually appealing. frame(height: 300): The video player is confined to a specific height, ensuring a clean layout. player.play(): This starts video playback. cornerRadius(10): This rounds the corners of the video view, making it visually appealing. frame(height: 300): The video player is confined to a specific height, ensuring a clean layout. Here's the code for the implementation shown: import AVKit
import SwiftUI

struct VideoPlayerView: View {
    private var player = AVPlayer(url: URL(string: "https://www.example.com/samplevideo.mp4")!)

    var body: some View {
        VStack {
            VideoPlayer(player: player)
                .frame(height: 300)
                .cornerRadius(10)

            HStack {
                Button("Play Video") {
                    player.play()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.blue)
                .cornerRadius(8)

                Button("Pause Video") {
                    player.pause()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.red)
                .cornerRadius(8)
            }
            .padding(.top, 20)
        }
        .padding()
    }
}

struct ContentView: View {
    var body: some View {
        VStack {
            Text("Welcome to Video Player")
                .font(.largeTitle)
                .padding()

            VideoPlayerView()
        }
    }
} import AVKit
import SwiftUI

struct VideoPlayerView: View {
    private var player = AVPlayer(url: URL(string: "https://www.example.com/samplevideo.mp4")!)

    var body: some View {
        VStack {
            VideoPlayer(player: player)
                .frame(height: 300)
                .cornerRadius(10)

            HStack {
                Button("Play Video") {
                    player.play()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.blue)
                .cornerRadius(8)

                Button("Pause Video") {
                    player.pause()
                }
                .font(.headline)
                .foregroundColor(.white)
                .padding()
                .background(Color.red)
                .cornerRadius(8)
            }
            .padding(.top, 20)
        }
        .padding()
    }
}

struct ContentView: View {
    var body: some View {
        VStack {
            Text("Welcome to Video Player")
                .font(.largeTitle)
                .padding()

            VideoPlayerView()
        }
    }
} The full series is available on my profile and the components can also be found at shipios.app/components . shipios.app/components shipios.app/components Happy Coding! 🎨 Happy Coding! 🎨

AVKit Integration in iOS 18 - #30DaysOfSwift

ARKit & LiDAR: Building Point Clouds in Swift (part 2)

Day 21: Custom Toggle Button, anyone? ⚙️ Today, we’re going to create a custom toggle button in SwiftUI. Implementing a Custom Toggle Button In this example, we’ll create a visually appealing custom toggle button that switches between on and off states. Code Example Here’s how you can implement a custom toggle button in SwiftUI: import SwiftUI

struct CustomToggle: View {
    @Binding var isOn: Bool // Binding variable for toggle state

        var body: some View {
            HStack {
                Text("Toggle Setting")
                    .foregroundColor(.primary) // Text color
                Spacer()
                // Custom square toggle design
                RoundedRectangle(cornerRadius: 5) // Rounded corners
                    .fill(isOn ? Color.blue : Color.gray) // Toggle color based on state
                    .frame(width: 60, height: 30) // Toggle size
                    .overlay(
                        Rectangle() // Square knob design
                            .fill(Color.white)
                            .frame(width: 26, height: 26)
                            .offset(x: isOn ? 15 : -15) // Move the square based on state
                            .animation(.easeInOut(duration: 0.2), value: isOn) // Animation for smooth transition
                    )
                    .onTapGesture {
                        isOn.toggle() // Toggle the state on tap
                    }
            }
            .padding() // Padding for the entire toggle
        }
    }

struct ContentView: View {
    @State private var isToggleOn = false // State to manage toggle status

    var body: some View {
        VStack {
            CustomToggle(isOn: $isToggleOn) // Custom toggle instance
            Text(isToggleOn ? "Setting is ON" : "Setting is OFF") // Display current state
                .padding()
        }
        .padding()
    }
}

@main
struct CustomToggleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    
} The full series is available on my profile, and the components can also be found at shipios.app/components. Happy Coding! 🎈 Day 21: Custom Toggle Button, anyone? ⚙️ Day 21: Custom Toggle Button, anyone? ⚙️ Today, we’re going to create a custom toggle button in SwiftUI. custom toggle button Implementing a Custom Toggle Button In this example, we’ll create a visually appealing custom toggle button that switches between on and off states. Code Example Here’s how you can implement a custom toggle button in SwiftUI: import SwiftUI

struct CustomToggle: View {
    @Binding var isOn: Bool // Binding variable for toggle state

        var body: some View {
            HStack {
                Text("Toggle Setting")
                    .foregroundColor(.primary) // Text color
                Spacer()
                // Custom square toggle design
                RoundedRectangle(cornerRadius: 5) // Rounded corners
                    .fill(isOn ? Color.blue : Color.gray) // Toggle color based on state
                    .frame(width: 60, height: 30) // Toggle size
                    .overlay(
                        Rectangle() // Square knob design
                            .fill(Color.white)
                            .frame(width: 26, height: 26)
                            .offset(x: isOn ? 15 : -15) // Move the square based on state
                            .animation(.easeInOut(duration: 0.2), value: isOn) // Animation for smooth transition
                    )
                    .onTapGesture {
                        isOn.toggle() // Toggle the state on tap
                    }
            }
            .padding() // Padding for the entire toggle
        }
    }

struct ContentView: View {
    @State private var isToggleOn = false // State to manage toggle status

    var body: some View {
        VStack {
            CustomToggle(isOn: $isToggleOn) // Custom toggle instance
            Text(isToggleOn ? "Setting is ON" : "Setting is OFF") // Display current state
                .padding()
        }
        .padding()
    }
}

@main
struct CustomToggleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    
} import SwiftUI

struct CustomToggle: View {
    @Binding var isOn: Bool // Binding variable for toggle state

        var body: some View {
            HStack {
                Text("Toggle Setting")
                    .foregroundColor(.primary) // Text color
                Spacer()
                // Custom square toggle design
                RoundedRectangle(cornerRadius: 5) // Rounded corners
                    .fill(isOn ? Color.blue : Color.gray) // Toggle color based on state
                    .frame(width: 60, height: 30) // Toggle size
                    .overlay(
                        Rectangle() // Square knob design
                            .fill(Color.white)
                            .frame(width: 26, height: 26)
                            .offset(x: isOn ? 15 : -15) // Move the square based on state
                            .animation(.easeInOut(duration: 0.2), value: isOn) // Animation for smooth transition
                    )
                    .onTapGesture {
                        isOn.toggle() // Toggle the state on tap
                    }
            }
            .padding() // Padding for the entire toggle
        }
    }

struct ContentView: View {
    @State private var isToggleOn = false // State to manage toggle status

    var body: some View {
        VStack {
            CustomToggle(isOn: $isToggleOn) // Custom toggle instance
            Text(isToggleOn ? "Setting is ON" : "Setting is OFF") // Display current state
                .padding()
        }
        .padding()
    }
}

@main
struct CustomToggleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    
} The full series is available on my profile, and the components can also be found at shipios.app/components . shipios.app/components shipios.app/components Happy Coding! 🎈

How to Create a Custom Toggle Button in iOS 18 - #30DaysOfSwift

Day 19: Tell Your Users About The Progress ⏳ Welcome to Day 19 of the #30DaysOfSwift series! Learn today about how to implement a progress bar in your SwiftUI app. Why Use Progress Indicators? User Feedback: They inform users that a task is in progress, improving the overall user experience. Task Transparency: Users can gauge how long they might need to wait, which can reduce frustration. Modern UI: Adding progress indicators enhances the aesthetics and functionality of your app. Example Use Case: Implementing a Progress Bar In this example, we’ll create a simple progress bar that updates as a task progresses. import SwiftUI

struct ContentView: View {
    @State private var progress = 0.0 // State variable to track progress

    var body: some View {
        VStack {
            ProgressView("Loading...", value: progress, total: 100) // Progress bar
                .progressViewStyle(LinearProgressViewStyle()) // Style of the progress bar
                .padding()

            Button("Start Loading") {
                startLoading() // Start the loading process
            }
            .padding()
        }
        .padding()
    }

    func startLoading() {
        progress = 0.0 // Reset progress
        for i in 1...100 {
            DispatchQueue.main.asyncAfter(deadline: .now() + Double(i) * 0.1) {
                progress = Double(i) // Update progress
            }
        }
    }
}

@main
struct ProgressIndicatorApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    }
} Now, it’s your turn! Try adding progress indicators to your app to keep users informed during loading processes! P.S. Check out full series at shipios.app/componenets Happy Coding! 🎉 Day 19: Tell Your Users About The Progress ⏳ Day 19: Tell Your Users About The Progress ⏳ Welcome to Day 19 of the #30DaysOfSwift series! Learn today about how to implement a progress bar in your SwiftUI app. progress bar Why Use Progress Indicators? User Feedback: They inform users that a task is in progress, improving the overall user experience. User Feedback : They inform users that a task is in progress, improving the overall user experience. User Feedback Task Transparency: Users can gauge how long they might need to wait, which can reduce frustration. Task Transparency : Users can gauge how long they might need to wait, which can reduce frustration. Task Transparency Modern UI: Adding progress indicators enhances the aesthetics and functionality of your app. Modern UI : Adding progress indicators enhances the aesthetics and functionality of your app. Modern UI Example Use Case: Implementing a Progress Bar In this example, we’ll create a simple progress bar that updates as a task progresses. import SwiftUI

struct ContentView: View {
    @State private var progress = 0.0 // State variable to track progress

    var body: some View {
        VStack {
            ProgressView("Loading...", value: progress, total: 100) // Progress bar
                .progressViewStyle(LinearProgressViewStyle()) // Style of the progress bar
                .padding()

            Button("Start Loading") {
                startLoading() // Start the loading process
            }
            .padding()
        }
        .padding()
    }

    func startLoading() {
        progress = 0.0 // Reset progress
        for i in 1...100 {
            DispatchQueue.main.asyncAfter(deadline: .now() + Double(i) * 0.1) {
                progress = Double(i) // Update progress
            }
        }
    }
}

@main
struct ProgressIndicatorApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    }
} import SwiftUI

struct ContentView: View {
    @State private var progress = 0.0 // State variable to track progress

    var body: some View {
        VStack {
            ProgressView("Loading...", value: progress, total: 100) // Progress bar
                .progressViewStyle(LinearProgressViewStyle()) // Style of the progress bar
                .padding()

            Button("Start Loading") {
                startLoading() // Start the loading process
            }
            .padding()
        }
        .padding()
    }

    func startLoading() {
        progress = 0.0 // Reset progress
        for i in 1...100 {
            DispatchQueue.main.asyncAfter(deadline: .now() + Double(i) * 0.1) {
                progress = Double(i) // Update progress
            }
        }
    }
}

@main
struct ProgressIndicatorApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView() // Main content view
        }
    }
} Now, it’s your turn! Try adding progress indicators to your app to keep users informed during loading processes! P.S. Check out full series at shipios.app/componenets shipios.app/componenets shipios.app/componenets Happy Coding! 🎉 Happy Coding!

Stories, News & Mentions about PODDIN

Poddin’s Stories on HackerNoon