Crossover: 2014

Chapter 148 An Application Worth Over [-] Million (Part [-])
It is precisely because the software workflow is mainly realized by mining the built-in functions of iOS.

This undoubtedly means that Lin Hui basically does not need to create anything new.

In this way, Lin Hui's workload is much smaller.

When users use the workflow software.

You can use the action modules provided by the software to form various tools to meet your own needs.

From the perspective of conventional software development, requirements determine design.

As a developer, what Lin Hui has to do is to get the corresponding action modules.

It is these action modules that give workflow a sense of control that users of this software have never experienced.

In workflow, users use action modules (built-in operations) to compose various tools.

The process is as easy as building blocks.

In practice, it may be easier than building blocks.

After all, building blocks sometimes requires some ideas.

But when creating command tools in the workflow software, there is basically no need to conceive at all.

When the user creates a command tool.

It is enough to have the normal thinking ability to deal with things.

For example, let's say a user wants to create an instruction tool in workflow software to automatically find the nearest movie theater and action route.

When the user is specifically created.

There is absolutely no need to think about any boring programming language related to programming.

All the user needs to consider is how he/she usually uses the mobile phone to find the nearest movie theater and how to operate the route.

This question, the user can think of the answer to the question with almost no effort.

What they usually have to do when doing this is to search for movie theaters, select the nearest movie theater, and display the route to the target movie theater.

Now that the answer has been thought out, all the user needs to do is to add the action modules corresponding to the above steps to the instruction tool that the user wants to design.

Then the user only needs to save the instruction tool, and can call this tool at any time in the future.

Let's name such a command tool "Find the nearest movie theater".

After the user has successfully built this instruction tool.

Just click the tool to execute the command.

The operations of searching, selecting and displaying routes can be automatically completed.

The whole process is basically smooth and smooth, very convenient.

Such a process allows people without programming skills to experience a sense of accomplishment similar to programming.

Although it is a little troublesome to perform such an operation in order to find a movie theater.

But after the user saves the corresponding command tool.

Encountering the corresponding scenario at a later time will greatly save the time required.

specific to the application scenario.

It could be even simpler.

Lin Hui can edit some common command tools to form a tool library.

Some of the more common needs of users do not need to repeat the work of reinventing the wheel.

Just add tools.

Although the tool library is more convenient and easier than the action module.

But as a developer, Lin Hui still needs to develop the corresponding action modules.

If you don't get the corresponding action module, get a tool library directly.

Then the software will lose its biggest feature.

In this case, workflow should not be called workflow.

Instead, it should be called a treasure chest.

In the iOS application market, this type of application is the most indispensable.

Developing corresponding action modules is not complicated in principle.

After all, many things come with iOS.

There are almost no action modules that really require Lin Hui to build from scratch.

Even if it involves some actions that need to be built from scratch.

Same problem.

Lin Hui has the complete workflow on his mobile phone in his previous life as a reference.

(End of this chapter)