Sql tables for excel-like table app

See more:

database

I am designing a database for a web app that shows a table which initially has a predetermined column names that can be of any type (text area, dropdown, date, textbox). The user also has the capability to add new columns, add new options for dropdown types, reorder the columns, hide and show column, and sort.(Excel-like behavior). The goal here is to provide the user a table in which they can input rows of data in which can be used for reporting and such. For multiple users, each user would have their own "view" (some users may opt to hide some columns) of that table.

What I have tried:

Given the requirements above the initial database design I come up with is:

[This table would house all the data in a row of the table and all its predetermined fields]
Table Name : AppRow
Columns : Id
          Name
          Phone
          Address
          Birthdate

[The tables below represent the new fields/column the user would add]
TableName : CustomColumnFields
Columns : Id
          Name

TableName : CustomColumnvalues
Columns : Id
          AppRowId
          CustomColumnFieldsId
          Value

[The purpose of this table is to have the value column[string] have the column names separated by comma that the user opt to choose to view e.g. user1 has name,phone or user2 has name,address,birth-date. It would basically dictate what columns should be presented to each user]
TableName : UserView
Columns : Id
          UserId
          Value

** Pleae note that we can assume the Database is exclusive ONLY for this set of users. They are are not sharing the DB to any other groups.

**** For this case also, the options for the dropdown type columns will be housed on a json file.

Having the requirements above and the structure, can anyone please help me assess if there are pitfalls, violation of design principle or any red flag?

I understand that what I am doing here is I am making the "Row" of the table as the entity of my application it is for the reason that I can easily insert data and edit data by row. This is in contrast if I design it per "Cell" or saving the values of each "Cell" on the database.

Please share your thoughts. Thank you.