App 1 of 100: JSONCrush
A developer tool for JSON validation with recursive tree parsing, syntax highlighting, and JSONPath extraction
Built today: 1h 18 minutes
Tests: 21/21 passing
Status: shipped
Learnings:
- CFBooleanGetTypeID() is the only way to distinguish JSON booleans from numbers.
- JSONSerialization returns NSNumber for both.
Day 120 – Onboarding Animations Completed, Faster Meme Loading & Moodboard Saving Fix 🚀
🔹 Finished Animations for Slide 3 & Slide 4
Wrapped up the animations for the last two onboarding screens.
Now all four onboarding slides have smooth, consistent animations, completing the entire onboarding flow experience.
🔹 JSON Serialization Added for MemePost (Major Performance Boost)
Added fromJson and toJson methods to the MemePost model.
This upgrade enables:
Parallel meme loading instead of slow sequential loading
Faster UI response times
More efficient caching
Cleaner data handling
Overall, the Home and Discovery screens now load memes significantly quicker.
🔹 Meeting Update – Onirudda Islam
The meeting was postponed.
He’ll share a new timing after 6 PM tomorrow.
🔹 Fixed Moodboard Saving Issue in Firestore
Previously the moodboard didn’t save properly due to profile creation timing.
Now it works perfectly:
Profile is created during meme upload itself
User ID is stored in SharedPreferences
Moodboard images stored in Firebase now save correctly using just the user ID
Even after reopening the app, the ID persists and saving works consistently.
🔹 Pending: Music anthem saving
The music anthem follows a different Firestore structure, so the current fix doesn’t apply.
Need to explore an alternative saving mechanism to finalize this.
#MemeMates#FlutterDev#OnboardingFlow#Animations#DataCaching#JSONSerialization#Firestore#PerformanceBoost#ParallelProcessing#MobileAppDevelopment#StartupLife#BuildingInPublic#IndiaStartups#TechFounder#StateManagement#DailyProgress#CleanArchitecture#FlutterPerformance#UIUX#MemeApp#ProductUpdate
lol of the day: Apple's JSONSerialization can throw NSExceptions. These cannot be captured in Swift. Gotta go back to ObjC and write a wrapper.
Ah, I love this platform.
github.com/steipete/Tachikom…
@RevenueCat@joshdholtz am I holding this wrong?
Metadata configured like this, but I get a hard crash when I try to access the subtitle value as it passes the string to JSONSerialization.
I recognize I should use the method with a default option, but I want an optional String
I have encountered weird JSON, but usually I can code around it with custom decoders. The honors for a truly difficult field goes to the 'error' field on replicate's Training object 🙇♂️. It causes both Decodable and JSONSerialization to blow up before any conformance methods even get called. I'm close to shipping a full Flux training flow for iOS/macOS, but need to work this one out first. @replicate little help please :) would love to chat with someone on your API team. Can send repros.
if you're using `JSONSerialization` to prettify your ugly JSON, make sure to that you know this bug exist.
quite annoyed that we're at iOS 17, and it hasn't been fixed yet 😤
📡 ¿Quieres aprender a crear PETICIONES HTTP en SWIFT
Explicamos conceptos como
- URLSession.shared
- Método dataTask
- Método resume()
- JSONSerialization
Video explicado paso por paso 👇
▶️ youtu.be/dU8eeng0VzE
📡 ¿Quieres aprender a crear PETICIONES HTTP en SWIFT
Explicamos conceptos como
- URLSession.shared
- Método dataTask
- Método resume()
- JSONSerialization
Video explicado paso por paso 👇
▶️ youtu.be/dU8eeng0VzE
One of the aspects of the article is the utilization of a custom Decodable container to drive dynamic, type-erased widgets through standard conformance.
It's much cleaner than I previously used, involving JSONSerialization to enable type-erased and independent components.
JSONDecoder: Simplicity
JSONSerialization: older but faster
Protocol Buffers: for very complex dataTypes. it is faster than the previous two
ZippyJSON: uses a c library called simdjson to decode. it is a direct replacement for JSONDecoder.
should be much faster yet simple