hackslash dot org

Show HN: My iOS app to practice sight reading (10 years in the App Store)

Posted: 2025-03-23 21:25:08

"Notes" is an iOS app designed to help musicians improve their sight-reading skills. Available on the App Store for 10 years, the app presents users with randomly generated musical notation, covering a range of clefs, key signatures, and rhythms. Users can customize the difficulty level, focusing on specific areas for improvement. The app provides instant feedback on accuracy and tracks progress over time, helping musicians develop their ability to quickly and accurately interpret and play music.

The Hacker News post titled "Show HN: My iOS app to practice sight reading (10 years in the App Store)" introduces an application specifically designed for musicians seeking to improve their sight-reading proficiency, a crucial skill for performing music accurately and fluently upon first encounter. The app, titled "Notes: Sight Reading Trainer" and available on the iOS App Store, represents a decade of development and refinement. It offers a comprehensive suite of tools and exercises tailored to various skill levels and musical preferences. The core functionality revolves around presenting the user with musical notation, which they must then interpret and, ideally, perform.

The app boasts a wide range of customizable features, allowing users to tailor their practice sessions to their specific needs. This includes options for selecting the clef (bass, treble, alto, tenor), key signature, time signature, and note range, enabling focused practice on particular musical elements. Users can further refine their training by choosing specific rhythmic patterns or melodic intervals they wish to concentrate on, facilitating targeted improvement in areas of weakness. The app's flexibility extends to instrument choice, theoretically accommodating any instrument capable of producing the displayed pitches, although it's primarily geared towards melodic instruments.

Beyond simply displaying notation, the app provides valuable feedback mechanisms. While the ideal usage would involve playing the notes on an instrument, the app incorporates a playback feature, allowing users to hear the correct rendition of the displayed passage. This auditory feedback serves as a valuable tool for self-assessment and reinforces the connection between visual notation and aural realization. Furthermore, the app tracks user progress over time, potentially motivating continued practice and providing a quantifiable measure of improvement in sight-reading ability. The post highlights the app's longevity in the App Store, suggesting a history of user engagement and ongoing development, implying a mature and well-tested application. Essentially, the app aims to be a versatile and effective digital tool for musicians of varying levels to hone their sight-reading skills conveniently on their iOS devices.

Summary of Comments ( 116 )
https://news.ycombinator.com/item?id=43456030

HN users discussed the app's longevity and the developer's persistence, praising the 10-year milestone. Some shared their personal sight-reading practice methods, including using apps like Functional Ear Trainer and various websites. A few users suggested potential improvements for the app, such as adding support for other instruments beyond piano and offering more customization options like adjustable clefs. Others questioned the efficacy of pure note-reading practice without rhythmic context. The overall sentiment was positive, acknowledging the app's niche and the developer's commitment.

The Hacker News post about the "Notes: Sight Reading Trainer" iOS app, which has been on the App Store for 10 years, generated several interesting comments.

Many users commended the developer for the app's longevity and consistent updates over a decade. They praised the commitment to maintaining and improving the app in a rapidly changing mobile landscape. Some long-time users chimed in, attesting to the app's usefulness in improving their sight-reading skills. They appreciated features like customizable key signatures, clefs, and rhythms, highlighting the app's adaptability to different skill levels and learning goals.

A common theme in the comments was the difficulty of creating and maintaining a successful app, particularly for a niche market like music education. Users expressed respect for the developer's perseverance and dedication to this specific area.

Several commenters discussed the importance of sight-reading for musicians and shared their personal experiences using various tools and techniques to practice. This led to a brief discussion about different approaches to sight-reading pedagogy.

Some comments also focused on technical aspects. One commenter asked about the development tools used, specifically inquiring about using SwiftUI and UIKit together. The developer replied, explaining their approach of integrating SwiftUI incrementally into the existing UIKit codebase, offering a practical example of managing a legacy codebase in the evolving iOS development ecosystem.

A few commenters shared their own preferred methods for sight-reading practice, suggesting alternative apps or resources. This wasn't a dominant part of the discussion but offered a glimpse into the broader landscape of sight-reading tools available.

Overall, the comments section reflected a positive reception to the app and appreciation for the developer's long-term commitment. The discussion provided a mix of personal experiences, technical insights, and pedagogical considerations related to sight-reading practice.

A few words about indie app business

permalink

Posted: 2025-02-28 02:59:24

Indie app development is a challenging business. While success stories exist, most indie apps don't achieve significant financial success. Marketing, discoverability, and competition from larger companies are substantial hurdles. Furthermore, the continuous need for updates and platform changes necessitates ongoing development effort, even without guaranteed returns. Despite the difficulties, some developers find the pursuit rewarding for the creative freedom and potential, albeit small, for financial independence. Ultimately, passion for the project is crucial for persevering through the demanding and often unprofitable reality of indie app development.

Charlie Monroe, in his blog post titled "A Few Words About Indie App Business," provides a comprehensive and somewhat disheartening perspective on the realities of independent software development for profit. He commences by acknowledging the allure of the indie app dream – a vision of financial freedom and creative autonomy achieved through the development and sale of one's own software. He contrasts this idyllic image with the often stark realities he has observed within the independent app development landscape.

Monroe meticulously details the challenges associated with achieving sustained success in this field. He argues that the vast majority of independent app developers struggle to generate significant revenue, highlighting the immense competition, the rapidly changing technological landscape, and the substantial time commitment required for marketing, customer support, and continuous product development. He elucidates the difficulty of accurately predicting future market trends and emphasizes that even apps that initially gain traction can quickly lose momentum as user preferences shift or competitors emerge with superior offerings.

A core element of Monroe's argument revolves around the fallacy of the "passive income" narrative frequently associated with app development. He underscores the ongoing effort necessary to maintain an app's relevance and functionality, including addressing bugs, implementing new features, and adapting to operating system updates. This continuous maintenance, he contends, often transforms the idealized notion of passive income into a demanding and time-consuming endeavor, more akin to running a small business than enjoying financial freedom.

Further elaborating on the complexities of app marketing, Monroe discusses the intricacies of app store optimization (ASO) and the challenges of attracting and retaining users in a crowded marketplace. He notes that even with a well-designed and functional app, success hinges heavily on visibility and discoverability, which often necessitate significant investment in marketing efforts. Furthermore, he touches on the ongoing pressure to adapt to changing user expectations and the need for consistent updates and improvements to remain competitive.

Finally, Monroe concludes his post by acknowledging that while the indie app business can be challenging, it can also be rewarding for those with realistic expectations and a strong work ethic. He encourages aspiring independent developers to thoroughly research the market, carefully consider the financial implications, and prepare for the significant time and effort required to build and maintain a successful app. He emphasizes the importance of understanding the long-term commitment involved and urges potential developers to approach the endeavor with a realistic understanding of the challenges and rewards inherent in the indie app business.

Summary of Comments ( 8 )
https://news.ycombinator.com/item?id=43201251

HN commenters generally agreed with the author's points about the difficulty of the indie app market. Several shared their own struggles with discoverability and monetization, emphasizing the importance of marketing and a unique value proposition. Some suggested alternative business models like subscriptions or focusing on niche markets. A few commenters pointed out the inherent luck involved in succeeding, while others questioned the sustainability of a purely indie approach, suggesting exploring contract work or other income streams for stability. The importance of managing expectations and enjoying the process was also highlighted.

The Hacker News post titled "A few words about indie app business" (linking to charliemonroe.net) generated a moderate discussion with a few interesting points raised in the comments section.

Several commenters focused on the challenges of marketing and discovery, echoing the author's concerns. One commenter highlighted the difficulty of competing with large companies that can afford extensive marketing campaigns, effectively drowning out smaller independent developers. They pointed out that even a truly great app can languish in obscurity without significant marketing efforts, a disheartening reality for many indie developers.

Another commenter discussed the shift in the app landscape, noting that the initial gold rush of the App Store has subsided. They suggested that the current market is much more mature and competitive, requiring a more sophisticated approach to both development and marketing than simply building a good app. This commenter also emphasized the importance of identifying a niche and catering specifically to its needs, rather than trying to appeal to a broad audience.

A further discussion thread delved into the specifics of marketing strategies for indie developers. One suggestion was to leverage content marketing by creating valuable resources related to the app's functionality, thus attracting potential users organically. Another commenter proposed exploring alternative app stores, although acknowledging that these often have smaller user bases and potentially less lucrative monetization options.

The practicality of relying solely on indie app development as a primary income source was also debated. Skepticism was expressed, with some commenters arguing that the odds of achieving significant financial success are slim. They suggested treating app development as a side project or hobby, rather than betting one's livelihood on it.

Finally, a few commenters shared their personal experiences, some recounting successes with niche apps, while others described the frustration of pouring effort into projects that ultimately failed to gain traction. These anecdotal accounts served to illustrate the realities of the indie app market, both the potential rewards and the significant challenges.

While not a highly active discussion, the comments on the Hacker News post offer valuable insights into the current state of indie app development, particularly the crucial role of marketing and the increasingly competitive nature of the market. They paint a picture of a landscape where passion and creativity alone are often insufficient, and a strong business strategy is essential for survival.

Watchdog ponders why Apple doesn't apply its strict app tracking rules to itself

permalink

Posted: 2025-02-14 13:12:22

A UK watchdog is investigating Apple's compliance with its own App Tracking Transparency (ATT) framework, questioning why Apple's first-party apps seem exempt from the same stringent data collection rules imposed on third-party developers. The Competition and Markets Authority (CMA) is particularly scrutinizing how Apple gathers and uses user data within its own apps, given that it doesn't require user permission via the ATT pop-up prompts like third-party apps must. The probe aims to determine if this apparent double standard gives Apple an unfair competitive advantage in the advertising and app markets, potentially breaching competition law.

The United Kingdom's Competition and Markets Authority (CMA), a governmental body responsible for ensuring fair competition and protecting consumer interests, has initiated an investigation into Apple's adherence to its own App Tracking Transparency (ATT) framework, specifically questioning whether the company applies the same stringent regulations to its own first-party applications as it does to third-party apps available on the App Store. The ATT framework, introduced by Apple in 2021, requires app developers to obtain explicit user consent before tracking their activity across other apps and websites for the purposes of targeted advertising. This framework has been lauded by privacy advocates but has simultaneously drawn criticism from advertising companies and some developers who argue it unfairly restricts their business models.

The CMA's probe centers around concerns that Apple may be engaging in a double standard, potentially giving its own apps an unfair competitive advantage by collecting and utilizing user data for personalized advertising without facing the same limitations imposed by ATT on external developers. This potential discrepancy raises questions of anti-competitive behavior, as it could allow Apple to leverage user data in ways unavailable to competitors, thus bolstering its own advertising business and potentially disadvantaging rival services. The investigation will delve into the specifics of how Apple handles data collection within its first-party apps, examining whether the company is truly adhering to the spirit and letter of the ATT framework or if it is employing alternative methods to circumvent the restrictions it places on others.

The CMA's investigation follows prior scrutiny of Apple's practices, reflecting broader concerns about the company's considerable power within the app ecosystem and the potential for anti-competitive conduct. The outcome of this investigation could have significant implications for Apple, potentially leading to regulatory interventions, enforced changes to its data collection practices, or even financial penalties if the CMA determines that Apple has indeed violated competition law. Furthermore, the investigation’s findings could influence policy discussions and regulatory approaches towards data privacy and competition in the digital marketplace, potentially setting precedents for how other large tech companies are scrutinized in the future. The CMA emphasizes the importance of ensuring a level playing field for all app developers, regardless of size or affiliation, and safeguarding consumer privacy in the increasingly complex digital landscape. The investigation is ongoing, and the CMA has not yet reached any conclusions regarding Apple's compliance with its own rules.

Summary of Comments ( 36 )
https://news.ycombinator.com/item?id=43047952

HN commenters largely agree that Apple's behavior is hypocritical, applying stricter tracking rules to third-party apps while seemingly exempting its own. Some suggest this is classic regulatory capture, where Apple leverages its gatekeeper status to stifle competition. Others point out the difficulty of proving Apple's data collection is for personalized ads, as Apple claims it's for "personalized experiences." A few commenters argue Apple's first-party data usage is less problematic because the data isn't shared externally, while others counter that the distinction is irrelevant from a privacy perspective. The lack of transparency around Apple's data collection practices fuels suspicion. A common sentiment is that Apple's privacy stance is more about marketing than genuine user protection. Some users also highlight the inherent conflict of interest in Apple acting as both platform owner and app developer.

The Hacker News post "Watchdog ponders why Apple doesn't apply its strict app tracking rules to itself" generated several comments discussing Apple's privacy practices and the UK's Competition and Markets Authority (CMA) investigation.

Several commenters expressed skepticism about Apple's claims of protecting user privacy, suggesting the company's motivations are primarily driven by profit. They point to Apple's own data collection practices within its pre-installed apps as evidence of a double standard. One commenter highlighted the irony of Apple boasting about user privacy while simultaneously collecting substantial amounts of user data for its own advertising business.

A recurring theme in the discussion revolves around the potential anti-competitive nature of Apple's App Tracking Transparency (ATT) framework. Some commenters argue that ATT disproportionately affects third-party advertising networks while benefiting Apple's own advertising platform. This sentiment is echoed in discussions about Apple's first-party data advantage, with some believing that Apple leverages the data it collects from its own apps and services to give its advertising business an unfair competitive edge.

One commenter brought up the point that Apple is under investigation in multiple jurisdictions for similar issues, suggesting a broader pattern of concern regarding the company's privacy practices and market dominance.

There's discussion around the technicalities of personalized advertising and the distinction between first-party and third-party data collection. Some commenters attempt to explain how Apple's data collection might differ from third-party trackers, but these arguments are met with counterarguments about the lack of transparency and user control over Apple's own data practices.

Some users express frustration with the lack of granular control over Apple's data collection within its own apps. They desire more options to opt out of specific data collection practices, rather than the current all-or-nothing approach for personalized ads.

Finally, a few comments mention the difficulty of regulating large tech companies like Apple, highlighting the complexities of navigating privacy concerns, competition regulations, and the rapid pace of technological advancements. They also discuss the challenges faced by regulators in proving anti-competitive behavior and effectively enforcing regulations in the digital advertising landscape.

Luck Be a Landlord Might Be Banned from Google Play

permalink

Posted: 2025-01-13 14:10:33

The popular mobile game Luck Be a Landlord faces potential removal from the Google Play Store due to its use of simulated gambling mechanics. Developer Trampoline Tales received a notice from Google citing a violation of their gambling policies, specifically the simulation of "casino-style games with real-world monetary value, even if there is no real-world monetary value awarded." While the game does not offer real-world prizes, its core gameplay revolves around slot machine-like mechanics and simulated betting. Trampoline Tales is appealing the decision, arguing the game is skill-based and comparable to other allowed strategy titles. The developer expressed concern over the subjective nature of the review process and the potential precedent this ban could set for other games with similar mechanics. They are currently working to comply with Google's request to remove the flagged content, though the specific changes required remain unclear.

The popular mobile game Luck Be a Landlord, a title that blends elements of slot machine mechanics with property management simulation, is facing the imminent threat of removal from the Google Play Store. This precarious situation has arisen due to the developer's staunch refusal to integrate changes demanded by Google pertaining to the game's depiction of simulated gambling. Google's policies, which aim to safeguard users from potential harm associated with gambling-like mechanics, specifically target the portrayal of simulated gambling as a path to financial gain. Luck Be a Landlord, with its core gameplay loop centered around spinning slots to acquire rent payments and upgrade properties, ostensibly falls within the purview of these regulations.

The developer, Dan, argues vehemently that Luck Be a Landlord is not, in fact, a gambling game. He contends that the game is fundamentally a strategy game, emphasizing the strategic choices players make regarding property acquisition and upgrades. While acknowledging the presence of randomized elements through the slot machine mechanic, he maintains that these elements are simply part of the game's overall design and do not constitute gambling in the traditional sense. Furthermore, he points out that the game does not offer real-world rewards or facilitate any form of monetary transactions related to the in-game mechanics, thereby further differentiating it from actual gambling.

Despite these arguments, Google appears resolute in its stance. The company has explicitly communicated to Dan that the game must be altered to comply with its policies, with suggested modifications including the removal of the slot machine visual metaphor or the introduction of alternative progression systems not reliant on simulated gambling mechanics. Dan, however, is resistant to these proposed changes, believing that they would fundamentally compromise the core gameplay loop and the very essence of Luck Be a Landlord. He perceives these demands as a form of censorship that stifles creative expression and undermines the artistic integrity of his game.

This impasse has created a tense standoff, with the ultimate fate of Luck Be a Landlord on the Google Play Store hanging in the balance. Dan faces a difficult choice: either acquiesce to Google's demands and potentially alter his game beyond recognition, or stand his ground on principle and risk the removal of his game from a major distribution platform, thereby significantly impacting its reach and accessibility to players. The situation highlights the ongoing tension between platform holders' content policies and developers' creative freedom, particularly in the increasingly complex landscape of mobile gaming.

Summary of Comments ( 122 )
https://news.ycombinator.com/item?id=42683567

Hacker News users discuss the potential ban of the mobile game "Luck Be a Landlord" from Google Play due to its gambling-like mechanics. Several commenters expressed sympathy for the developer, highlighting the difficulty of navigating Google's seemingly arbitrary and opaque enforcement policies. Others debated whether the game constitutes actual gambling, with some arguing that its reliance on random number generation (RNG) mirrors many other accepted games. The core issue appears to be the ability to purchase in-game currency, which, combined with the RNG elements, blurs the line between skill-based gaming and gambling in the eyes of some commenters and potentially Google. A few users suggested potential workarounds for the developer, like removing in-app purchases or implementing alternative monetization strategies. The overall sentiment leans toward frustration with Google's inconsistent application of its rules and the precarious position this puts independent developers in.

The Hacker News comments section for the linked article discusses the potential removal of the game "Luck Be a Landlord" from the Google Play Store due to its inclusion of simulated gambling. The discussion revolves around the fairness and consistency of Google's enforcement policies, the nature of gambling in games, and the potential impact on the game's developer.

Several commenters express confusion and frustration with Google's seemingly arbitrary enforcement of its gambling policies. They point out other games on the platform that contain similar mechanics, such as loot boxes or gacha systems, and question why "Luck Be a Landlord" is being singled out. Some speculate about the specific criteria Google uses to determine what constitutes prohibited gambling and suggest that the game's explicit real-world money theme might be a contributing factor. Others argue that the core gameplay loop itself, revolving around random chance and resource management, doesn't necessarily equate to gambling.

A significant portion of the discussion focuses on the impact this ban could have on the game's developer. Commenters express sympathy for the solo developer, highlighting the potential financial and emotional toll of losing a significant distribution platform. The perceived lack of clear communication and support from Google is also criticized. Some suggest alternative distribution methods, such as itch.io or direct sales, and encourage the developer to appeal the decision.

A few commenters delve into the broader discussion surrounding the definition of gambling in games. They debate whether the presence of real-world currency themes, the ability to purchase in-game items, or the element of chance are sufficient to classify a game as gambling. Some argue that "Luck Be a Landlord" falls into a gray area, while others maintain that its core mechanics are distinct from traditional gambling activities.

The overall sentiment in the comments section leans towards support for the game developer and skepticism towards Google's enforcement policies. Many express concerns about the potential chilling effect this ban could have on independent game developers, particularly those experimenting with unconventional mechanics. The lack of transparency and seemingly arbitrary nature of the ban are recurring points of contention.

Show HN: The App I Built to Help Manage My Diabetes, Powered by GPT-4o-Mini

permalink

Posted: 2024-11-18 00:07:55

A developer created "Islet", an iOS app designed to simplify diabetes management using GPT-4-Turbo. The app analyzes blood glucose data, meals, and other relevant factors to offer personalized insights and predictions, helping users understand trends and make informed decisions about their diabetes care. It aims to reduce the mental burden of diabetes management by automating tasks like logbook analysis and offering proactive suggestions, ultimately aiming to improve overall health outcomes for users.

A developer, frustrated with the existing options for managing diabetes, has meticulously crafted and publicly released a new iOS application called "Islet" designed to streamline and simplify the complexities of diabetes management. Leveraging the advanced capabilities of the GPT-4-Turbo model (a large language model), Islet aims to provide a more personalized and intuitive experience than traditional diabetes management apps. The application focuses on three key areas: logbook entry simplification, intelligent insights, and bolus calculation assistance.

Within the logbook component, users can input their blood glucose levels, carbohydrate intake, and insulin dosages. Islet leverages the power of natural language processing to interpret free-text entries, meaning users can input data in a conversational style, for instance, "ate a sandwich and a banana for lunch," instead of meticulously logging individual ingredients and quantities. This approach reduces the burden of data entry, making it quicker and easier for users to maintain a consistent log.

Furthermore, Islet uses the GPT-4-Turbo model to analyze the logged data and offer personalized insights. These insights may include patterns in blood glucose fluctuations related to meal timing, carbohydrate choices, or insulin dosages. By identifying these trends, Islet can help users better understand their individual responses to different foods and activities, ultimately enabling them to make more informed decisions about their diabetes management.

Finally, Islet provides intelligent assistance with bolus calculations. While not intended to replace consultation with a healthcare professional, this feature can offer suggestions for insulin dosages based on the user's logged data, carbohydrate intake, and current blood glucose levels. This functionality aims to simplify the often complex process of bolus calculation, particularly for those newer to diabetes management or those struggling with consistent dosage adjustments.

The developer emphasizes that Islet is not a medical device and should not be used as a replacement for professional medical advice. It is intended as a supplementary tool to assist individuals in managing their diabetes in conjunction with guidance from their healthcare team. The app is currently available on the Apple App Store.

Summary of Comments ( 73 )
https://news.ycombinator.com/item?id=42168491

HN users generally expressed interest in the Islet diabetes management app and its use of GPT-4. Several questioned the reliance on a closed-source LLM for medical advice, raising concerns about transparency, data privacy, and the potential for hallucinations. Some suggested using open-source models or smaller, specialized models for specific tasks like carb counting. Others were curious about the app's prompt engineering and how it handles edge cases. The developer responded to many comments, clarifying the app's current functionality (primarily focused on logging and analysis, not direct medical advice), their commitment to user privacy, and future plans for open-sourcing parts of the project and exploring alternative LLMs. There was also a discussion about regulatory hurdles for AI-powered medical apps and the importance of clinical trials.

The Hacker News post titled "Show HN: The App I Built to Help Manage My Diabetes, Powered by GPT-4-Turbo" at https://news.ycombinator.com/item?id=42168491 sparked a discussion thread with several interesting comments.

Many commenters expressed concern about the reliability and safety of using a Large Language Model (LLM) like GPT-4-Turbo for managing a serious medical condition like diabetes. They questioned the potential for hallucinations or inaccurate advice from the LLM, especially given the potentially life-threatening consequences of mismanagement. Some suggested that relying solely on an LLM for diabetes management without professional medical oversight was risky. The potential for the LLM to misinterpret data or offer advice that contradicts established medical guidelines was a recurring theme.

Several users asked about the specific functionality of the app and how it leverages GPT-4-Turbo. They inquired whether it simply provides information or if it attempts to offer personalized recommendations based on user data. The creator clarified that the app helps analyze blood glucose data, provides insights into trends and patterns, and suggests adjustments to insulin dosages, but emphasizes that it is not a replacement for medical advice. They also mentioned the app's journaling feature and how GPT-4 helps summarize and analyze these entries.

Some commenters were curious about the data privacy implications, particularly given the sensitivity of health information. Questions arose about where the data is stored, how it is used, and whether it is shared with OpenAI. The creator addressed these concerns by explaining the data storage and privacy policies, assuring users that the data is encrypted and not shared with third parties without explicit consent.

A few commenters expressed interest in the app's potential and praised the creator's initiative. They acknowledged the limitations of current diabetes management tools and welcomed the exploration of new approaches. They also offered suggestions for improvement, such as integrating with existing glucose monitoring devices and providing more detailed explanations of the LLM's reasoning.

There was a discussion around the regulatory hurdles and potential liability issues associated with using LLMs in healthcare. Commenters speculated about the FDA's stance on such applications and the challenges in obtaining regulatory approval. The creator acknowledged these complexities and stated that they are navigating the regulatory landscape carefully.

Finally, some users pointed out the importance of transparency and user education regarding the limitations of the app. They emphasized the need to clearly communicate that the app is a supplementary tool and not a replacement for professional medical guidance. They also suggested providing disclaimers and warnings about the potential risks associated with relying on LLM-generated advice.

Stories with Tag App Store

Show HN: My iOS app to practice sight reading (10 years in the App Store)

Summary of Comments ( 116 ) https://news.ycombinator.com/item?id=43456030

A few words about indie app business

Summary of Comments ( 8 ) https://news.ycombinator.com/item?id=43201251

Watchdog ponders why Apple doesn't apply its strict app tracking rules to itself

Summary of Comments ( 36 ) https://news.ycombinator.com/item?id=43047952

Luck Be a Landlord Might Be Banned from Google Play

Summary of Comments ( 122 ) https://news.ycombinator.com/item?id=42683567

Show HN: The App I Built to Help Manage My Diabetes, Powered by GPT-4o-Mini

Summary of Comments ( 73 ) https://news.ycombinator.com/item?id=42168491

Summary of Comments ( 116 )
https://news.ycombinator.com/item?id=43456030

Summary of Comments ( 8 )
https://news.ycombinator.com/item?id=43201251

Summary of Comments ( 36 )
https://news.ycombinator.com/item?id=43047952

Summary of Comments ( 122 )
https://news.ycombinator.com/item?id=42683567

Summary of Comments ( 73 )
https://news.ycombinator.com/item?id=42168491