Nfc

2 posts

toss3 min readCurated summary

It Almost Ended Up Ugly - The Making of Toss Front 2

Toss redesigned its Front 2 payment terminal by addressing real-world usability problems rather than settling for technically workable solutions. The redesign moved NFC to the front, made the card reader field-replaceable, and reworked the internal structure to simplify removal. The result was a smaller, cleaner device that improved both customer experience and repairability. ## Moving NFC to the Front - The first-generation terminal placed NFC on the right side because other components interfered with the signal. - This was inconvenient in narrow retail spaces, where users had little room to tap cards or phones. - Several alternatives were tested: - Moving the card reader upward made card insertion awkward and strained users’ wrists. - Enlarging the top made the vertically oriented terminal look excessively long and displaced the camera, complicating barcode and face-payment use. - Placing NFC around the camera caused interference, producing camera shake and reducing recognition accuracy. - The team reframed the problem by asking whether the display’s metal backing could be replaced. - A customized plastic backing allowed NFC signals to pass through while reinforced glass preserved the display’s rigidity. - Despite higher manufacturing complexity and cost, the design was successfully mass-produced, enabling reliable front-facing NFC without sacrificing appearance. ## Designing a Replaceable Card Reader - The first-generation card reader was integrated into the main body, so failures required repairing or replacing the entire terminal. - Repairs took more than a week on average, forcing stores to use backup devices and distributors to maintain extra inventory. - Front 2 introduced a docked, replaceable card reader designed for easy on-site replacement. - A USB-C connector was selected because users already understand how to connect and disconnect it. - The connector provided stable attachment without exposing additional brackets or mechanisms, preserving the product’s clean appearance. ## Making Removal Simple - Once the reader used USB-C, the team needed a way to remove it without adding buttons, levers, or protruding parts. - The simplest approach was to insert the reader from the front and push it out from behind, but existing power and network connections blocked the necessary space. - Instead of adding another mechanism, the team redesigned the internal layout from scratch. - The circuit board and connectors were tilted toward the top of the device, requiring redesigned and inverted cable components. - This created enough room to remove the reader without tools. - The revised layout also made the cables easier to see and connect. ## Results of Front 2 - Front-facing NFC made payments more natural on crowded counters. - The USB-C dock reduced the difficulty of replacing a failed card reader. - The terminal became smaller while retaining its visual simplicity and design quality. - Front 2 surpassed the first generation’s sales immediately after launch, while previous customer complaints shifted toward positive feedback. ## Building Quality Through Persistent Questions - The article argues that product quality comes from repeatedly challenging an acceptable technical solution. - The team focused on finding answers that were right for users and the overall product experience, not merely answers that functioned. - For similar design problems, the recommended questions are: - Can everyone use the design easily, including in edge cases? - What is the fundamental problem? - Is the current solution truly the best one? - If not, can the problem and solution direction be redefined? The practical lesson is to keep revisiting the problem until the solution is not only feasible, but genuinely appropriate for users.

Read original(opens in new tab)
discord3 min readCurated summary

Discord Patch Notes: October 1, 2024

Discord’s October 1, 2024 patch focuses on mobile performance, storage efficiency, usability improvements, and broad bug fixes. Android users should see smoother chat rendering and lower resource usage, while iOS users may benefit from substantially reduced data storage. The update also introduces desktop Soundboard improvements, macOS screen-sharing refinements, and Animated WebP support. ## Mobile Performance and Storage - Android chat rendering improvements reduced slow frames by up to 60%, depending on the device. - Android chat-list memory usage fell by approximately 12%, making scrolling through message histories smoother. - Mobile server-list virtualization keeps only visible servers loaded: - Memory usage improved by 14% for users in many servers. - CPU usage improved by 25%. - Mobile unread indicators now consistently appear above the correct message, even with many unread messages. - iOS data-store changes reduced storage usage for the most affected 1% of users from 5.7 GB to 1.7 GB. - Fixed iOS message search results beyond the first page and crashes involving certain NFC hardware keys. - Resolved tablet orientation-detection issues and several Android problems involving read states and mobile keyboards. ## New Features and Interface Updates - macOS screen-sharing startup now has a more consistent and streamlined interface. - Desktop received a redesigned Soundboard interface for easier sound navigation and interaction. - Web and desktop clients can now play Animated WebP attachments, offering smoother playback and potentially lower bandwidth usage. - Electron was upgraded to version 32, with expected incremental performance and crash-reduction benefits. - Pasting a URL over an existing link now properly replaces the original URL instead of creating unexpected Markdown behavior. - Activity Status now correctly displays PS5 games. - The green acceptance check mark has returned to friend-request notifications. ## Interface and Navigation Fixes - Corrected visual issues involving emoji pickers, GIF categories, profile status bubbles, avatar decorations, fonts, borders, and themed search filters. - Fixed navigation problems in GIF categories, the Shop, Friends UI, mutual-friend lists, and profile popouts. - Improved accessibility and navigation indicators so they are no longer cut off in several profile and list views. - Corrected layout issues in Student Hub, channel settings, server settings, Notification Center, and message requests. - Fixed Quests links, Server Guide icons, role expansion behavior, and the display of permission descriptions on mobile. - Restored functionality for the Toggle Overlay hotkey after switching applications with Alt-Tab. - Corrected several modal and popup layering issues, including stickers, Soundboard uploads, and quest cards. ## Reliability and Content Fixes - Fixed crashes when viewing deleted channels in Audit Log with ModView open. - Corrected poll countdown text as polls approach closure. - Member verification and rules-agreement indicators now reflect the correct state. - Fixed incorrect game-presence names appearing in Japanese. - Resolved issues with rate-limited or frozen GIF categories. - Corrected timeout duration display in moderation views. - Fixed profile customizations failing to load on the first Shop attempt. ## Chat Improvements - Fixed mobile chat layout issues, including the missing “Jump to Bottom” button and overlapping composer elements. - Android web embeds now scale correctly instead of cutting off image content. - Corrected message-height calculations and action-sheet handle placement. - Prevented Avatar Decorations from being clipped at the top of chat. Discord’s update is primarily a reliability and performance release. Users—especially those on Android, iOS, or with many servers—should benefit from smoother navigation, lower resource consumption, and fewer interface defects as the changes roll out across platforms.

Read original(opens in new tab)