Hi, we're Storyie 👋

Thanks for stopping by! I'm an engineer building a simple diary app that I'd want to use myself.

App Features

• Write on mobile, publish to the web - Because that's how I actually write
• Clean and simple - Built by an engineer who values simplicity

The tech side

If you're curious about the engineering:

• Mobile app built with React Native and Expo
• Web publishing powered by Next.js
• Cross-platform rich text editor using Lexical
• Everything runs on a modern stack designed for speed and reliability

We share our technical decisions and architecture on our blog because we believe in building in public.

What's next

We're just getting started and would love to hear what you think. As a small team (okay, mostly just me right now), your feedback directly shapes what gets built next.

Feel free to reach out anytime. I read every message.

Happy writing!

— The Storyie Team

Today I focused on SEO optimization and UX improvements.

Late at night, I unified the old brand name "storywrite" to "storyie" across the codebase. Updated 6 files including config files and documentation.

Added blog pages to the sitemap so Google can discover our technical blog posts.

Finally, solved the duplicate content issue between subdomain pages and canonical URLs. Implemented canonical URL and noindex meta tags to ensure search engines index the correct pages. Created a new seo.ts utility for this.

#SEO

SEO, Supabase, and a New Brand

Strengthened SEO for diary entries by adding avatar images to Open Graph and Twitter Cards, and created a mobile app preview component. Also implemented structured data for FAQs to improve search result appearance.

Worked on internationalization of the codebase by unifying locale settings to en-US and translating all comments to English. Significantly refactored the Supabase client, improving cookie management and OAuth authentication flow. Also fine-tuned homepage SEO metadata and reorganized deployment procedures.

Wrapped up the day by improving Google Sign-in configuration, enhancing debugging and error handling.

It was a productive day with wide-ranging improvements including SEO enhancements, authentication flow refinements, and rebranding. The Supabase client refactoring and app slug change were particularly significant changes that will serve as a foundation for future development.

#SEO

Implemented Note Management Features

Today I worked on developing the note feature for the Storyie Expo app.

I implemented a large set of note management features. I created a new note creation screen, note detail screen, and floating action buttons (delete, share, and public/private toggle). I also built an autosave hook with debounce functionality. Added localization for all 10 languages. Over 1,800 lines of code added in total.

After that, I improved the title field focus state management. Made it so the keyboard toolbar hides when the title is focused on the note creation and editing screens. This improved the UX when entering titles.

Overall, the note feature is now fully functional and has the same feel as the diary feature.

#Note

Public Pages & Infrastructure

Implemented the public diary page feature with metadata generation for SEO. Added multi-language support to the sitemap.

Simplified the URL structure by removing language prefixes (e.g., /en/d/xxx). Streamlined the share functionality accordingly.

Configured CloudFront and Cloudflare settings: disabled cache for API authentication routes, implemented stage-based domain aliases, and moved

configuration values to environment variables.

Completed internationalization work, including translating Japanese comments to English and localizing confirmation dialogs for delete, publish,

and share actions.

Enhanced UUID validation for slug parameters.

Summary: Public page infrastructure is now in place. Primary focus was on deployment configuration and i18n.

#Infrastructure