Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ This guide will explain how to set up Quark, use it, and customize it.
quark_inside_index
modules
faq
visual_quark_scripts_program

Indices and tables
==================
Expand Down
59 changes: 59 additions & 0 deletions docs/source/visual_quark_script_program.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
++++++++++++++++++++++++++++
Visual Quark Scripts Program
++++++++++++++++++++++++++++

Introducing Our Plan to Develop a Visual Programming Tool for Quark Scripts
---------------------------------------------------------------------------

Quark scripts are a powerful tool for detecting and analyzing mobile security. However, they can be complex and challenging for users who are not familiar with programming. To overcome this challenge, we are pleased to announce our plan to develop a visual programming tool that simplifies the Quark script organization process, making it easy for anyone to organize Quark scripts using a simple UI interface.


What Goals Do We Want To Achieve?
=================================

Our goal is to make Quark script programming accessible to everyone and remove the barriers that often come with traditional programming languages. We believe that by providing a visual tool to organize Quark scripts, we can significantly reduce the time and effort required to write complex scripts while also making it more intuitive for users who are not familiar with programming.

Roadmap
=======

The following table is the roadmap for this product. We are still in the early development stage, and the first phase is mainly focused on completing the main functions to enable users to operate the system intuitively, view Quark script diagrams, and assemble new Quark scripts on their own.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"initial development stage" would be more suitable than "early development stage".

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "and now we focus on ... in their own way" would be more intuitive than "and the first phase is mainly focused on .... on their own".


.. list-table:: Roadmap
:widths: 25 25 25 25
:header-rows: 1

* - Timeline
- Q1 & Q2
- Q3
- Q4
* - Releases
- Baseline
- Version 1.1
- Version 2 – Delight
* - Desired Experience
- - Intuitive
-
-
* - Must-Have Capabilities
- - Seeing visualized Quark scripts
- Using a User Interface to modify the flow and parameters in a Quark script
- To be determined
- To be determined
* - User Experience Improvements
-
-
-
* - Performance Improvements
-
-
-
* - Growth Experiments
-
-
-


Join Our Team
=============

Our team of developers is currently working on building a prototype of the tool and we are looking for talented individuals who are passionate about making Quark script programming accessible to everyone. If you're interested in joining our team, don't hesitate to get in touch with us.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Our developers are" could be better than "Our team of developers is".

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "and we need more ... making tools accessible to everyone" would be more positive than "and we are looking for ... making Quark script programming accessible to everyone.", how do you think ?