Tweet
Finishing up my offline/caching/syncing feature. It's been a beast. Visualizing the project as a huge, heavy, stone block has helped me get through it. Everyday, I try to move that block forward, if only an inch. Soon, I will get this across the finish line ๐Ÿ’ช๐Ÿ

#buildinpublic
โœ… App runs off of Core Data
โœ… Core Data syncs with web server
โœ… Detect network connectivity and block features that need internet
๐Ÿ”ฒ Loading existing users' data into Core Data

It's been grueling, but the hard work is making the idea a reality.

#buildinpublic
It always amazes me how much time and suffering can be saved with a little planning and effort thinking through a problem, and how often I'd just rather try something and hope for the best.
#buildinpublic
Started syncing data back to the web server from core data. Opening up a can of worms and the complexity is increasing. Aware of the risk, and don't feel great about it, but I'm committed to making this happen!
#buildinpublic
Rebuilt Seasons to run off of Core Data. Now I'm going to add various flags to my local storage to know when and what to sync to my web server. Slow going, but learning a lot. Looking forward to having a streamlined syncing mechanism and responsive app.
#buildinpublic
Getting the hang of this and steadily replacing api requests with Core Data fetches. I'm so eager for this to be done, but there's so much left to do and refactor. Constantly reminding myself to just focus on the next step.
#buildinpublic
A lot to refactor in order to use Core Data, but I'm excited about the increase in responsiveness. I've learned about storing files as binary data and Core Data's external storage option, but audio is my current hurdle because I need access to a URL for playback.
#buildinpublic
Happy Monday! Today I will be moving forward with my Core Data implementation. Hasn't been too hard to CRUD using Core Data. My uncertainty is in syncing with my web server and maintaining data integrity. Intimidating, but it must be done! ๐Ÿ’ช
#buildinpublic
Struggled learning about caching and was hitting dead ends. Now thinking about the offline journaling experience I want to provide. Core Data here we go... In other news, Seasons Journaling recently made its first two subscription sales! Nice little morale boost.
#buildinpublic
Spent hours yesterday watching videos and reading about offline caching solutions that I didn't understand. I'm reminding myself that I've been here before. My process, perhaps as an inexperienced app dev, includes feeling lost before a path forward becomes clear.
#buildinpublic
Today I'm going to list off the design feedback I need from a friend before releasing a tab navigation UI. While I'm waiting for feedback, I'll find a good video to watch about caching to support offline journaling - a feature that I desperately want for myself.

#buildinpublic
Been pretty quiet lately. I could put more effort into trying, without sacrificing authenticity. The last two weeks have not been about coding. It feels like I'm starting up again.

Currently working on a tab navigation to open up room for a premium feature๐Ÿ”๏ธ

#buildinpublic
Question for the indie maker community - how does your approach to marketing change as you continue to build your product? Do you feel like only marketing your product when X is done?
#buildinpublic
Question for the indie maker community - how does your approach to marketing change as you build your product?
#buildinpublic
Slowed down for a few days after getting the subscription paywall released and spent a day hiking in the mountains to clear my head. Now back to the original climb ๐Ÿ”๏ธ
#buildinpublic
Seasons Journaling v1.11 is now live! It adds a subscription paywall that unlocks the ability to create multiple journals and gives access to all customization options. A lengthier recap & thoughts on next steps is on IH if you're interested bit.ly/3tepsXx
#buildinpublic
Making this UI come to life today! Copy still pending. Level of uncertainty is high for this paywall, but gotta start somewhere. Iโ€™ll adjust as needed. Progress > Perfection. #buildinpublic
A direct result of cold-outreach, in recent days a few users have pointed out 1) an edge case crash related to date formatting, 2) a poor UX where a keyboard covers a text field for smaller screen phones, and 3) an issue with a beta subscription offer I'm testing.

#buildinpublic
Sometimes it takes a lot of time, effort, and stress just to be able to take the next step. You can question how hard something is supposed to be or how easy it might be for someone else, or you can just decide that you aren't going to stop.

#buildinpublic