Postflyr

Postflyr halves your workload and doubles your reach by centralizing posts across platforms. Automate, analyze, and engage effortlessly with AI-powered scheduling. Post smarter, grow faster!

Comment

Postflyr: Centralizing and Supercharging Your Online Presence

Inspiration

The 555 rules for social media growth and online presence revolve around three core pillars: consistency, context, and community. Specifically, they emphasize posting frequently (5), tailoring each message to the correct format (5), and engaging meaningfully across platforms (5). We wanted an app that lives by these rules—helping users manage multiple social media channels consistently, ensure context-fit for different platforms, and foster authentic community engagement.

What It Does

Our app centralizes all your social media posting needs—draft once and publish everywhere. We initially planned an AI-powered caption generator to:

  1. Analyze each social platform’s style and best practices.
  2. Optimize captions, so they’re perfectly tailored for each target audience.
  3. Schedule and publish your posts seamlessly, allowing you to focus on growth and community.

Though the AI module is still in progress, we have the foundational system that connects multiple platforms in one place for streamlined posting.

How We Built It

  • Frontend: Built with Vite (TypeScript + React) for an intuitive, responsive UI.
  • Backend: Implemented with FastAPI (Python) to manage user data, handle OAuth tokens, and orchestrate publishing logic.
  • OAuth & API Integrations: We integrated each platform’s OAuth flow to obtain short-lived and long-lived access tokens (Instagram, Twitter, Facebook).
  • Infrastructure: Since Instagram demands an HTTPS redirect_uri, and our app ran on HTTP locally, we used an HTTPS tunnel to forward traffic from a secure port to our local FastAPI server.

Challenges We Ran Into

  1. Short-Lived & Long-Lived Tokens: Managing Instagram tokens was trickier than expected—there were extra steps to exchange short-lived for long-lived tokens.
  2. HTTPS Redirects: Instagram’s OAuth requires a secure redirect URI, so we had to set up a tunnel mapping https://localhost:3443 to our http://localhost:8000 FastAPI server. This led to some confusion until we aligned all configurations.
  3. Mixed Documentation: Integrating multiple social APIs meant juggling different OAuth scopes and endpoints. We found official docs to be either outdated or scattered, so we tested calls manually (via curl) to confirm parameters.
  4. Time: Unfortunately, our time management was not optimal, which prevented us from fully implementing every planned feature within the challenge period.

Accomplishments

  • Cross-Platform Posting: Demonstrated the ability to log in via Instagram’s (and others’) OAuth, generate tokens, and partially automate posting flows.
  • Streamlined Infrastructure: Got a Vite frontend + FastAPI backend working in tandem, even with the HTTPS tunnel requirement for the Instagram callback.
  • 555 Rules Integration: Baked the 555 methodology directly into our approach, encouraging consistent, context-aware posting for stronger audience engagement.

What We Learned

  • Token Management: Each platform has slightly different token expiry and refresh mechanics—short-lived → long-lived flows took extra care to implement.
  • HTTPS Requirement: Even for local dev, OAuth can demand secure callbacks, forcing us to adopt tunnels for a correct setup.
  • Documentation Gaps: Dealing with partially outdated or incomplete docs required hands-on experimentation with curl and Postman to fill in the blanks.

What’s Next

  1. AI Caption Engine: Deploy advanced text-generation tuned to each platform’s character limits, tone, and audience expectations.
  2. Deeper Analytics: Provide detailed insights about post performance, best times to publish, and user engagement.
  3. Full OAuth Integration: Polish and finalize the short/long-lived token management so users can seamlessly connect, refresh, and maintain posting permissions without friction.
  4. Enhanced Scheduling & Collaboration: Create team workflows for content calendars, letting multiple contributors plan, preview, and approve upcoming posts in one place.

Conclusion

At ConUHacks IX, we’ve built ** Postflyr** to embody the 555 rules by unifying posting, amplifying content quality, and empowering communities to engage meaningfully. From a Vite front end to a FastAPI back end, we tackled short-lived & long-lived tokens, secure tunnels for HTTPS, and disparate API docs to bring this concept to life. We look forward to refining the AI component and integrating further advanced features that make cross-platform publishing even more seamless.

Built With

Share this project:

Updates