Best practice for Monday.com specific apps?

[joseffb]

Hey all, I’ve got some newbie questions regarding making an app for general usage using the Monday.com framework.

I’m still trying to get my head around some basic concepts, so I apologize if these questions seem naive.

1. When building a new feature>board – this is actually a board view and not a board per say. Correct? If so, do I need to create a specific board – with specific fields – using the API create board, or do I need to make a view that works with any board template? I would love to be able to make a board template and have the board view apply that template but I can’t find any documentation on how to do this.

2. I’m assuming that the I need to add fields in the feature edit area, then import them into my react app via the api settings command. will this pull just those fields, or pull the entire content of the board using this view, or do I need to use the api boards query command.

3. is there a React App component for implementing the Monday Table component? or do I need to add my own table component for my view?

I know what I want to build, and it seems like trying to use Monday storage and tables is actually harder then just building the app with its own backend using aws serverless node (which I don’t want to do).

[dsilva]

Hey @joseffb - welcome to the community!

1. Correct - this is a board view (similar to if you were creating a calendar view or any of our other natives ones). It then reads the data from the main board.

2. I believe this is correct - a great way to see this in action for yourself is to check out our quickstart guide to see how this is managed on both the monday end and server end.

3. I don’t believe there is a component we provide on our end, but there are a few open source ones out there that can be utilized.

Let me know if we can help with anything else.

-Daniel