Member Avatar for BungeeBones

Hi all,

I operate a web directory and made it so that other websites can install it and pull the categories and links from my database (an effortless web directory).

I recently discovered I could install it in my FaceBook account too very easily. All that someone else needs to do to get one also is to register at my site, get the script and install it on their website. Then, they build their faceBook page and pull their webpage/directory into their faceBook with the FaceBook iframe.

But I am wondering that since this system doesn't use FaceBook for any transport of data does this usage technique really constitute being an app? Technically all that FaceBook is doing is importing text from my site.

Thanks

  • 2 Contributors
  • 2 Replies
  • 189 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by BungeeBones
shahzebkhan commented: good +1

Dani AI

Generated

Short answer: what describes is an embed of external content into a Facebook page, not a full Facebook Platform app in the sense of using Facebook authentication and the Graph/Open‑Graph features. It will work as a lightweight page tab or iframe widget, but it won't get the platform-level features that come from registering an app with Facebook.

's RSS idea is useful as a portability layer. Publishing the directory as an RSS or JSON feed makes it easy for a tab, a server-side connector, or third‑party services to pull updates with minimal effort. Advantages: simple to implement, cacheable, easy for other sites to consume. Limitations: feeds are read‑only and carry limited metadata and personalization; they don't grant platform permissions or let the site post on users' behalf or read user data.

When the project needs personalized experiences, social distribution, analytics or App Center exposure, converting to a true Facebook app is the right move. That typically means registering an app (App ID/secret), supporting OAuth login, and calling the platform APIs to read/write or publish structured Open‑Graph data. That adds development and (when needed) an app‑review step for extended permissions, but it unlocks features like per‑user content, social stories, and deeper integration.

Actionable checklist for the project owner:

  • Offer a feed (RSS/JSON) as the canonical, versioned export for easy consumption and caching.
  • For quick embedding, allow framing (check X‑Frame‑Options) and serve over HTTPS.
  • If personalization or posting is required, register a Facebook app, add OAuth login, and use the platform APIs.
  • Verify mobile behavior and current Facebook developer requirements before investing in app review.

Note: Facebook's platform rules and technical details change over time; consult the current Facebook Developer documentation before implementing platform‑specific features.

Member Avatar for peterson5052

use Rss feed as a source.

Member Avatar for BungeeBones

I understand RSS feeds but don't understand what you mean by using it "as a source". Do you mean feed the web directory's categories and links page as an RSS feed? What would be the advantages/disadvantages?

But I am looking for the answer to whether I should modify or add FaceBook interoperability at some level (if this current method isn't an app).

Thanks for the input though

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.