mapbox / mapbox/mapbox-scenekit

SceneKit SDK Feature Requests

Open
#69 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
232
Forks
50
PR merge metrics
No merged PRs in 30d

Description

Hello everyone! The team is laying out the roadmap for the SDK, looking forward to an official v1.0 release. We’ve drafted a list of items that should be done.

In the interests of transparency and meeting the needs of you, the developer, I am adding a list of some of our work items below and would welcome your input on the relative priority of items from your perspective. Feel free to comment and also add any items you see as important.

A partial list of items are:

- Scaffolding for proper v1.0 SDKs (CI, develop branch, etc.)
- Better support for custom Mapbox Studio map style URLs
- Crash fixes for some occasional crashes that we’ve seen
- Revise API. Switch to delegate pattern for texture/heightmap loading instead of callbacks. We are open to feedback from our users on the best pattern for you, but this is our plan.
- Increased integration with Mapbox Mobile iOS SDK
- Additional sample projects

Once we have a settled list, we’ll be cutting tickets for each item. Please provide feedback below. We want to make sure we prioritize the changes that would help you the most.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a roadmap discussion rather than an implementation ticket, and it names no files, tests, or specific entry point. Review the proposed CI and develop-branch scaffolding, Mapbox Studio URL support, crash fixes, delegate-based loading API, iOS SDK integration, and sample projects; work is not considered defined until these items are split into scoped tickets with clear priorities and completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.