About
I design and build small, high signal experiments that become products. I work at the…
Services
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
-
-
-
-
-
-
-
Courses
-
Color In Context And Practice
-
-
Color Theory
-
-
Computer Art
-
-
Format And Design
-
-
Graphic Design Theory And Practice
-
-
Hardware, Software, And Networks
-
-
Internet Applications; Systems;Computers And Society
-
-
Production And Web Design
-
Other similar profiles
Explore more posts
-
Ankit Mohanta
Just helped another team solve Firebase crashes that were costing them $2,000/day in lost revenue Firebase + React Native integration doesn't have to be a nightmare. After debugging hundreds of these crashes, I've identified the 4 most common issues that kill apps in production: ✅ Initialization timing disasters ✅ Authentication memory leaks ✅ Firestore query explosions ✅ Build configuration bombs The worst part? These often work fine in development but explode when real users touch them. I just published a complete guide with bulletproof code examples and the exact solutions that have saved countless app launches. #ReactNative #Firebase #MobileDevelopment #AppDevelopment
-
Mohamed Mostafa
Software engineers fear the AI that will take their job while the real danger I see should be in companies and solution owners themselves. Products that you spent years and tons of dollars for buildng selling it for whatever the number of subscriptions is can now be easily cloned and it costs nothing but the Gen AI subscription and some small resources. I am really curious of how the scene will look like after maybe Q2 of 2026. The development that business owners needs to follow “not to fail in the common nokia example” is now talking days not years like all used before!! #ArtificialIntelligence #GenerativeAI #SaaS #StartupLife #ProductManagement #SoftwareEngineering #TechTrends #DigitalTransformation #Innovation #FutureOfWork #Entrepreneurship
2 Comments -
Bartek Widlarz
When your favorite audio libraries in React Native start fighting each other... 🥊 We just published a case study breaking down how we tackled chaos in the audio layer when 𝘦𝘹𝘱𝘰-𝘢𝘷 and 𝘳𝘦𝘢𝘤𝘵-𝘯𝘢𝘵𝘪𝘷𝘦-𝘷𝘪𝘴𝘪𝘰𝘯-𝘤𝘢𝘮𝘦𝘳𝘢 wouldn't cooperate. Here’s what that actually meant in practice: Unbalanced volume between the user's voice and playback, conflicts over control of the native audio session and unpredictable and unstable behavior of a key app feature 🚀Our solution: a custom native module that took 100% control. - Why it matters for any app with audio/video: - Reliability is fundamental – users don't tolerate glitches. - Full control over native APIs unlocks new possibilities. - Sometimes you have to build your own tools to deliver a 10/10 product. If you're building in React Native and facing similar challenges, this one's for you. You'll find the link to the case study in the first comment. #ReactNative #CaseStudy #AudioEngineering #MobileDevelopment
2 Comments -
GreatFrontEnd
TypeScript utility types aren't just syntactic sugar, they're the difference between writing types that work and types that scale in production. If you're serious about front-end development in 2025, these 5 utility types will transform how you handle data flow: 👉 Essential Utility Types: 1. Partial<T>: Makes all properties optional Perfect for update forms and PATCH requests 2. Pick<T, K>: Extracts specific properties Ideal for component props and API responses 3. Omit<T, K>: Excludes unwanted properties Clean data sanitization and secure APIs 4. Record<K, T>: Creates key-value mappings Type-safe objects and configurations 5. ReturnType<T>: Extracts function return types Consistent API responses and composable functions The Reality Check Most developers overcomplicate types or avoid them entirely. These 5 utilities handle 90% of real-world type transformations without custom logic. Stop reinventing the wheel. Start building type-safe applications that actually ship. 📌 Ready to master TypeScript fundamentals? Practice these in real projects: https://lnkd.in/gUK5it4Z 💬 Which utility type saves you the most time in daily development? #TypeScript #FrontEndDevelopment #WebDevelopment #TypeSafety #greatfrontend
9 Comments -
Visoft, Inc.
There's something fascinating happening right now with how developers approach cross-platform development, and I think we're at an inflection point. For years, the conversation was binary: build native or build once and compromise. React Native changed that narrative by proving you could write JavaScript and get genuinely native experiences on iOS and Android. But what I'm noticing is that many teams still treat it as a shortcut rather than a strategic choice. The real opportunity isn't about speed to market anymore. It's about maintaining code quality and developer velocity without sacrificing the user experience that native platforms deserve. When you're thoughtful about framework selection and architecture, React Native becomes less about cutting corners and more about smart resource allocation. The teams I see winning aren't the ones chasing the fastest deployment. They're the ones asking better questions upfront: What does our user base actually need? Where does native code make sense? How do we structure this so future developers can maintain it confidently? If you're evaluating your approach to mobile development right now, that's the conversation worth having. What's driving your framework decisions these days?
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content