Looking for experienced SketchUp Ruby developer for lightweight data-extractor extension

[br51]

Hi everyone,

I’m looking for an experienced SketchUp Ruby extension developer for a small paid task, and I would also appreciate general guidance from people who know the SketchUp plugin ecosystem well.

My background is in architecture / interiors / renovation. I’m working on a broader project that helps design software send structured project/model data into an external coordination system, so project information can continue into cost, time, procurement, approvals, and project memory instead of staying trapped inside separate design files.

For SketchUp, the first version is intentionally lightweight.

V1 goal:
Build a SketchUp Ruby extension that reads useful model data and sends structured JSON to an HTTPS endpoint.

Rough V1 scope:

• installable .rbz extension
• Windows + Mac support if practical
• run on manual save / save trigger
• recursively traverse groups and component instances
• preserve parent/child hierarchy
• include persistent IDs where available
• extract object names
• extract tags/layers
• extract object type
• extract bounding box / dimensions
• extract existing attribute dictionaries / metadata where available
• separate component definition data from placed component instance data where practical
• POST structured JSON to an HTTPS endpoint
• save a local JSON/log file if POST fails
• include sample JSON output and basic install/config instructions

For V1, I do not need live sync, writeback, model editing, or a complex UI.

Later, there may be a V2 with bidirectional features, such as:

• writing project IDs/status back into SketchUp attribute dictionaries
• detecting meaningful changes after an object is linked
• selecting/highlighting objects from backend-provided IDs
• sending selected object information back to the backend
• placing components from a library file with metadata attached

I am trying to be careful not to build V1 in a way that blocks V2 later.

If you are an experienced SketchUp Ruby extension developer and this sounds like something you can help with, please reply or message me.

I would also appreciate advice from the community on:

1. whether this should be built purely as a SketchUp Ruby extension
2. any important limitations around persistent_id, entityID, attribute dictionaries, or save observers
3. what a good V1 architecture should include so V2 does not require a rewrite
4. where experienced SketchUp Ruby developers usually look for this kind of paid work

Thank you — I appreciate any guidance.