The Final PDF
The Final PDF
Solve/Review Interface - the software application that is used to manage the creation and modification of digital con
tent
Editor - the part of the Solve/Review Interface that is used for writing the content of the PM Solution
Previewer - the part of the Solve/Review Interface that serves as a preview of what a certain PM Solution written in t
he Editor will look like for the User in the Photomath App
Job - represents the specific action performed with a certain task and the related material (solving or reviewing)
Example - represents a Task for which the PM Solution is already written and which is similar to the Task given in t
he Solve/Review Interface
Import - the action of copying the content of the Example PM Solution into the Editor
Solving Step - a unit of the PM Solution that provides a piece of information, it can contain text, LaTeX, PM Solver,
and Visual Content
Solution Step - a Step that represents an overview of the Task solution after the solving procedure has been written i
n the Solving Steps
PM Solution - consists of a(ny) number of Solving Steps (sometimes none are needed) and one Solution Step; repres
ents the entire content of all Solving Steps and the Solution Step
Text Content - represents the basic textual elements (words, sentences) of which the PM Solution is made
LaTeX Content- represents the basic LaTeX elements (mathematical symbols and objects such as expressions, varia
bles, etc.) of which the PM Solution is made
Inline LaTeX - LaTeX used for writing math symbols that are a part of a textual paragraph
Block LaTeX - LaTeX used for all statements made up of math symbols which are written as a separate paragraph
Visual Sequence - a unit of the PM Solution used to display two or more consecutive and related graphs/sketches/tab
les, it is perceived as one Solving Step with two or more Substeps
Math Sequence – a unit of the PM Solution that can be used for manual calculations in the Input-Description-Output
, it has at least three Substeps and it visually imitates a Solving Step with PM Solver
Sequence Substep - a unit of the Visual Sequence or the Math Sequence that provides one piece of information (one
Visual Content or one step of the calculation)
Primary Color - represents the BLUE color that is used for coloring Text Content, LaTeX Content and Visual Conte
nt
Secondary Color - represents the GREEN color that is used for coloring Text Content, LaTeX Content and Visual C
ontent
Tertiary Color - represents the ORANGE color that is used for coloring Text Content, LaTeX Content and Visual C
ontent
Math Sequence LaTeX Color – represents the RED color that is used for coloring LaTeX Content within Substeps o
f a Math Sequence (except for the first one)
PM Solver - A Photomath software that provides automated solutions for different kinds of math problems. The soft
ware can be used to solve any math problem that it supports.
Hint - an external link that is attached to a part of the Text Content in a Solving Step and it provides a definition and/
or a formula that serves as a reminder of a certain math concept that the User has learned
Input - Description - Output - represents a specific form of a Solving Step (often several consecutive Solving Steps)
that is used when algebraic manipulations (or calculations) are performed manually, it is often abbreviated to IDO
Warning - If there is a yellow triangle in the Editor, it means that there is a Warning. A Warning points to a common
mistake in a PM Solution which does not affect the User’s understanding of the PM Solution and the task with whic
h the Solution can still be saved.
Error - If there is a red triangle in the Editor, it means that there is an Error. An Error shows that a certain necessary
condition for a PM Solution is not (yet) satisfied. If any of the necessary conditions are not satisfied, the Solution ca
nnot be saved.
Methodical
Coherent
Economical
A detailed description of each Solution Quality is given below. Also, at the links given below each Solution Quality,
you can see a Task and its corresponding PM Solution. Read them carefully and notice how each Solution best repr
esents the given Solution Qualities.
Methodical
Task-solving methods and procedures, vocabulary and intellectual concepts have to be appropriate for the age and pr
eviously acquired knowledge of the User who will read the PM Solution to learn from it.
Solutions have to be educational - providing explanations of underlying mathematical concepts instead of just infor
ming the student.
Explanations have to be easy to follow, with simple sentence structure whenever possible.
To provide better clarity, a PM Solution should be enriched with Visual Content such as graphs, sketches or tables w
henever appropriate.
https://portal.photomath.net/task/3GYDXQJG
https://portal.photomath.net/task/W5Q2X1NG
https://portal.photomath.net/task/PV884Y7V
https://portal.photomath.net/task/MVZ4893G
https://portal.photomath.net/task/2GXL74NG
Coherent
Each Step has to be concise, brief and substantial. It should convey a complete statement.
Information given in a single Step must follow from the preceding Steps or from the context of the task. There shoul
d be a clear relation between consecutive Solving Steps.
The step-by-step solution should provide clear and understandable information and it should be easy to follow.
https://portal.photomath.net/task/B53YYY4G
https://portal.photomath.net/task/PVLQAAZ5
https://portal.photomath.net/task/2GX3362V
https://portal.photomath.net/task/1VERZXAG
https://portal.photomath.net/task/654AD8PV
Economical
Consider the effort put in creating the PM Solution and the impact it has upon a User's learning process.
The effort shouldn’t be greater than the impact the PM Solution will have.
Create all the necessary solving procedures and visuals but do not spend more time and resources than necessary.
https://portal.photomath.net/task/2GXL8Q2G
https://portal.photomath.net/task/E579N3AG
https://portal.photomath.net/task/E579XN4G
https://portal.photomath.net/task/W5QNKNK5
https://portal.photomath.net/task/3GYDE6JG
Header
DASHBOARD - home page, containing a welcome message and a link that leads you to the Solve/Review tab, to so
lve or review tasks. Here you can also find your referral link, which you can use to recommend the Photomath Portal
to interested friends, earning money if they qualify.
TRAINING - here you can choose one or more math areas in which you want to become a proficient Photomath Mat
h Expert, start tests and training for the math area(s) you chose and see an overview of your status and proficiency fo
r each math area at any moment
SOLVE/REVIEW - here you solve and review tasks from the math field or fields in which you became a qualified P
M Math Expert
PAYMENTS - here you can see your payouts and the status of each solving or reviewing job you performed
DEMO - here you can try all of the features and see what solving and/or reviewing looks like
STANDARDS - here you can open a website with all information needed to successfully solve tasks and review Sol
utions; you’ll learn more about this website later in this course
Use your name in the right corner to access your profile, where you can check your personal information, agreement
s and proficiency status, or to log out.
Demo
The DEMO tab imitates the Solve/Review Interface, so you can use it to try all of the features that Solve/Review Int
erface contains. You can check all the buttons the Editor contains, how PM Solver works or what can be found in th
e Base of Hints. You can also find out what each part of the Solve/Review Interface looks like and find out the purp
ose of each element in the Interface.
There is also a question mark button, called Start intro. Its purpose is to navigate you through the Solve/Review Inte
rface and to describe each button, feature or part of the Interface, to help you learn or to serve as a reminder.
Photomath Solution Rules are the basic criteria that must be fulfilled in order for a PM Solution to qualify as properl
y written. More precisely, if any rule is broken, the PM Solution is considered incorrect and requires modification.
To ensure high standards of Photomath Solutions, each solving procedure must adhere to the following rules:
The Solving Steps must provide a detailed explanation of the PM Solution, all required calculations or added Visual
Content.
Each Solving Step in the PM Solution must be brief. It should contain one complete statement or provide one new c
onclusion.
Visual Content, PM Solver or Block LaTeX must never be the only content of a Step. A Step with these elements m
ust include text or text and LaTeX that describes them.
In other words, the solution of the task must contain the procedure for obtaining the answers to all the questions aske
d in the task, which means that it is also necessary to provide Visual Content if required. There are different types of
tasks, for some the solving procedure involves finding the answer to only one question, and for some the solving pr
ocedure involves finding the answers to multiple questions. Also, in some tasks the solving procedure includes const
ructing a shape or body, in some it is necessary to conclude something from the given information, while some tasks
require coming up with an example.
Further, keep in mind that the User in the Photomath App will find it easier to process information that is presented
gradually. In order to facilitate the User's understanding, make sure that no Solving Step is crowded with too much i
nformation. Divide Solving Steps so that each contains one complete statement or presents one conclusion.
Generally, the Text Content of each Solving Step should be no more than a couple of sentences in no more than two
paragraphs. There are Warnings for too many characters in a Step and too many characters in a paragraph, use them
as guidelines in this matter. If there is additional content, such as Block LaTeX paragraphs, Visual Content or the P
M Solver, try to restrict the Text Content to one paragraph.
Also, make sure you never have just Visual Content in a Step, just Block LaTeX or just PM Solver without any expl
anation. The point is not just to give the answer, but to provide the User with an explanation about what is being don
e in a particular Step.
Correct PM Solution
The whole PM Solution has to be mathematically correct. That includes correct calculations, the correct use of graph
s, the correct use of math concepts and math terminology.
In other words, it is necessary to use math symbols, calculations and concepts that are appropriate for a certain situat
ion, and also that any Visual Content added is correct. If any Hints are added, they must also be suitable for the cont
ext. Always double-check to make sure that all the math terms you used or mathematical objects you wrote are prop
erly written and correctly shown in the Previewer.
LaTeX
Write all mathematical objects in LaTeX. This includes variables, numbers, formulas, symbols, years, amount of day
s, measurements, etc.
The following requirements must be respected:
All mathematical objects/symbols have to be written in LaTeX. You can find needed LaTeX commands for a great n
umber of math situations here.
Mathematical objects written in LaTeX and the PM Solver must be shown correctly and be clearly and completely v
isible in the Previewer. If a LaTeX expression or its part is displayed incorrectly, recheck it in the Editor and fix it so
that the Previewer shows it correctly.
The reason why all mathematical objects are written in LaTeX is that the use of LaTeX for mathematical symbols is
a common standard when writing mathematical texts.
Therefore, whenever there is some mathematical and/or numerical character, make sure you write it in LaTeX.
Language (1)
Write the whole solving procedure for a task in English.
Use full sentences in each Step of the PM Solution. For example, one standalone math expression is not acceptable i
n a PM Solution.
Start sentences with capital letters and use appropriate punctuation marks.
Use full words, without abbreviations.
Answer the task question directly, precisely, and without giving a complex explanation in one sentence. Use several
short sentences instead of one complex sentence.
Write either imperative sentences to give instructions or neutral statements to provide information or conclusions. T
he text should never directly refer either to you as the Math Expert or to the final User reading the Solution. For this
reason, it is essential that you do not use pronouns "I", “we” or “you” when writing your PM Solutions.
In other words, in order to provide a complete solution, the explanatory sentences must also be complete. Also, mak
e sure that all thought processes needed for understanding are represented fully, as if you are tutoring the User in per
son. Since the sentences must be complete, write explanations without abbreviations.
Also, it is important that the sentences are not too complicated, because it is easier for the User to follow a few simpl
e sentences than one complicated one. For this reason, use simple sentence structure whenever possible.
Further, the Photomath Solution should provide explanations and instructions to the User, so each sentence should ei
ther be a statement giving information or an instruction given in imperative form. The sentences that directly refer to
you as the Math Expert or to the User reading the Solution such as “We will calculate the difference.” or “You have
to add the numbers”, should never appear in PM Solutions. For these reasons, the pronouns “I”, “you” or “we” are n
ever allowed in the PM Solution, but pronouns that refer to the person or the object in the Task Content can be used
regularly, as in the sentences: “She bought 3 apples” or “They own one car more than their neighbors”.
With all written above, also make sure all your sentences are written in English language. That includes writing a ful
l stop at the end of a sentence and writing a colon at the end of sentences that introduce elements such as Block LaT
eX or the PM Solver in the following paragraph.
A direct answer to the task question must be given in the Solution Step, obtained by calculating or deducing in the S
olving Steps. If there is more than one question, then all of the questions must be answered.
The elements that can be used in the Solution Step are text, LaTeX and Visual Content, but there cannot be more tha
n one graph/sketch/table.
If the Solution Step needs to contain more than one Visual Content, choose only one.
If the task doesn’t require specific answers or it requires explaining or proving a certain phenomenon, then the Soluti
on Step contains a summary of all the Solving Steps or the main idea used in solving.
The Solution Step should be an independent statement (or several independent statements). It shouldn’t start with w
ords that refer to the Solving Steps such as “therefore”, “hence” or “so”. It also shouldn’t directly mention Solving S
teps.
In other words, the point is to use the Solving Steps to explain how to obtain the answer(s) to the question(s) asked i
n the task, and to use the Solution Step to provide (only) the required answer(s).
The Solution Step can contain Text, LaTeX or Visual Content. Any Visual Content must be connected to a textual d
escription and any LaTeX expression must either be part of a complete sentence or be introduced by a complete sent
ence.
Some tasks require multiple answers. If the answers that need to be provided are textual and not visual, write all of t
he required answers in the Solution Step.
Only one image can be placed in the Solution Step, so if for example the task requires two graphs to be drawn in the
same coordinate system, they can be displayed in one image. If the task requires two distinct visuals, such as two gra
phs in separate coordinate systems, or a graph and a table, then (only) one of them (the more important one, where a
pplicable) should be placed in the Solution Step.
There are also tasks that don’t require specific or simple answers, such as verifying the identity. In those cases, since
the answer to the task would be the entire solving process, verification is done through Solving Steps and the Soluti
on Step contains the list of concepts that were used to verify the identity (or, in other similar questions often a summ
ary of the solving procedure).
Coloring
Within a Step, the corresponding elements of the Visual Content, Block LaTeX, text or Inline LaTeX have to be col
ored using the same color.
Numbers, values or variables substituted into the formula given by the Hint or in the Input-Description-Output form
Relevant elements in Visual Content and in the corresponding parts of the text/LaTeX description:
When presenting new or added elements in Visual Content, they should be colored both in Visual Content and in the
description
When reading from a graph/sketch/table, relevant elements mentioned in a certain Step/Substep should be colored b
oth in Visual Content and in the description
The change happening from Input to Output in the Input-Description-Output form
In other words, the only reason to use colors is to emphasize the relation between corresponding parts of text, Visual
Content, Inline LaTeX and Block LaTeX. Colors focus the User’s attention on important relations within a Step. Th
ey must be used in the situations listed above, but they can also be used to emphasize relation in any other situation t
hat may not have been mentioned, as long as it makes sense. Random colors or colors added to emphasize an elemen
t, without relating it to any other element, are not allowed by this rule.
Visual Content (1)
Create any Visual Content on your own, using the proper colors. Visual Content should be mathematically correct, a
nd all important elements should be clearly visible in the Previewer.
Any Visual Content added to a PM Solution must be created by the Math Expert writing this Solution. The only exc
eption is if appropriate Visual Content is found within another PM Solution. Never use visuals found in Task Conten
t or outside of PM Solutions or Standards.
When creating Visual Content, use only the allowed colors in appropriate shades: primary (blue), secondary (green)
and tertiary (orange). Sketches that represent real-life situations can be colored using other colors, but only if they d
on’t have to be color-coordinated with any part of the description.
All Visual Content has to be mathematically correct (this is mainly covered by the Math rule).
All relevant elements of Visual Content have to be shown in the Previewer. They must be clearly displayed and easy
to read.
Visual Content is the collective name for graphs, sketches and tables. It is created using various programs, of which
we recommend Geogebra, Illustrator and Figma. You will learn how to create Visual Content, especially using our T
able Editor and GeoGebra, later in your solve training. This rule (with all other Solution Rules) provides several con
ditions that must be met in any Visual Content you create.
If you need an image to explain the procedure towards the solution, it is recommended that you create Visual Conten
t. If you need to visualize something, the User probably also needs to visualize it to understand the Solution.
Visual Content should always be paired with a proper description: either plain text or a combination of text and LaT
eX.
Input-Description-Output form
All algebraic manipulations within the Solving Steps must be written in the following form: Input-Description-Outp
ut.
The Input of a Solving Step must be the Output of the preceding one.
Input and Output are paragraphs written in mathematical language, using math symbols, so write them in Block LaT
eX.
A description is an explanatory sentence that specifies the change happening from Input to Output.
When manually solving math problems, each Step should be written in Input-Description-Output form, where Input
and Output are mathematical statements that are put in Block LaTeX, and the sentence that connects them describes
the change that occurs from Input to Output. Description is regular text announcing the change from Input to Output,
so it is usually written in imperative. Also, Inline LaTeX often appears in the Description. Therefore, the Input-Des
cription-Output form looks as follows:
Input-Description-Output form
Also, when multiple consecutive Steps are written in Input-Description-Output form, we set the Input of the followi
ng Step as the Output of the Step that precedes it.
Common mistakes
While our team reviewed written PM Solutions, we noticed that some mistakes are more common than others. We cr
eated a list of those mistakes below, together with instructions on how to correct them, to help you avoid them when
writing your PM Solutions.
Always make sure you are using the correct terminology to describe mathematical objects. For instance, distinguish
expression/equation/inequality, or congruent/equal. If approximate values are emphasized, it has to be clear from the
sentence by using terms like “about”, “around” or “approximately”.
Correct symbols should also be used. The symbol “=” signifies equality and is used only for exact values while the s
ymbol “\approx” signifies approximation and is used for rounded and approximate values.
If you are using a Hint of a Theorem to prove a statement, make sure it refers to the correct Theorem and not its Con
verse. For example, the Parallelogram Diagonals Theorem states that the diagonals of a parallelogram bisect, while t
he Parallelogram Diagonals Converse states that if the diagonals of a quadrilateral bisect, that quadrilateral is a paral
lelogram.
2. Not answering all the questions of the task
Once you write your PM Solution, re-read the task to make sure all the questions have been answered. If additional e
xplanations are required, include them in the Solution Step.
All the required verifications, Visual Content (graphs, diagrams), explanations, or proofs, have to be included in the
Solution.
3. The wrong solving method is used in the PM Solution
Make sure that if a method is required by the task, you use this method to solve the task. Also, if a certain method is
unsuitable for the knowledge level of the intended User, don’t use it (you can judge the expected knowledge level by
the math field). For instance, the minima and maxima of a function in an Algebra task should not be calculated usin
g derivatives.
If you are using the PM Solver, always double-check which solving process it uses, to ensure it corresponds to the o
ne required by the task or that it is appropriate to the field. For example, if a system of equations should be solved us
ing elimination, make sure that this method is within the PM Solver, rather than substitution or some other method.
4. Copying the original graph/sketch/table from the Task Content
Never copy the original parts of the Task Content, since it is intellectual property of its creator. Create your own Vis
ual Content in one of the recommended software (Geogebra, Adobe Illustrator, Figma), or using a software of your c
hoice, and include it in the Solution. If you find Visual Content appropriate for your Solution in another, already wri
tten PM Solution, you can (re)use it.
5. LaTeX or Visual Content doesn’t render properly in the Previewer
Always take a look at the Previewer to check if everything included in the PM Solution is rendered properly. It is ve
ry important, because the Previewer shows how the PM Solution appears for the User in the Photomath App.
Make sure that each LaTeX expression is written correctly, so it can be rendered correctly. Do not ignore lines in the
Previewer that point out the wrong use of LaTeX.
Make sure that included Visual Content is not too big or too small for the dimensions of a Step. Every object or nota
tion shown in the Visual Content must be visible and easy to read in the Previewer.
6. Wrong use of color-coordination
The only reason to use colors is to emphasize the relation between corresponding parts of the Visual Content, Block
LaTeX, text or Inline LaTeX within the same Step, so do not color-coordinate elements that appear in different Step
s. In each Step, the use of colors is independent of how they are used in the other Steps.
7. Wrong use of Input-Description-Output Form
Input and Output are mathematical statements, each of them written in Block LaTeX. Do not write more than one Bl
ock LaTeX paragraph for Input and Output because a Step would be crowded with too many elements and the Input-
Description-Output Form rule would be broken.
Description is a textual paragraph that may contain Text and Inline LaTeX Content. Write a complete sentence that s
pecifies the change happening from the Input to the Output.
8. Wrong color shades
Only 3 colors are available for Text/LaTeX Content in the Editor: primary (blue), secondary (green) and tertiary (ora
nge). When you create your own Visual Content, also use only these colors, with the given color codes. Do not use r
andom shades of blue, green or orange color because the Visual Content rule would be broken.