RastcodeS

If your app is going to have some data, and even more if that data is going to change over time, than you should probably get a database. Whether you need SQL, or No-SQL, you can count on me, but what we need to figure out together are the entities. That sounds like a scary word, but in database design it really means stuff.

This "stuff" we separate into 4 groups:

• People (your customers, employees...)
• Things (your products, projects)
• Places (your sales departments...)
• Events (like an individual sale)

Once we figure all this "stuff" out, we start the database design.

Creating a RESTful API is completely optional. Basically, it allows us to make an independent program, that includes your whole business logic, runs on the Web, but has no User Interface. Why would I want an app without a user interface, you ask? Well, it will allow you to have multiple interfaces.

Let's say you initially want a website, but then your business grows and you decide, you want a mobile app, that pretty much does the same thing. Stage left comes REST to the rescue, as you now only need another user interface and not a whole new program

But remember, it's completely optional.

Whether you decide on a RESTful API or not, the Back end has to be done. It can be as big, or as small as you like, but what does it really mean?

The back end is where the core work happens. The smallest example would be a simple contact form, which allows your customers to communicate with you via email. Also, if we make a database, we are going to need a way to work with it, or in tech terms, do CRUD operations.

What is that? An acronym of course:

• Create - add new things to the database
• Read - get items stored in the database
• Update - edit existing things
• Delete - remove unwanted stuff

That is only the beginning of course and one size does not fit all. If you're building a monster, then Java with Spring is your choice, but if your appetites are smaller, PHP with Laravel will suffice. Alternatively, if you want to play with the cool kids, you might want a Node/MERN app. Contact me, so I can help you figure out, what you might need and what tech you'd like to use.

Security in Apps comes in many forms, but it's safe to say, it's crucial for a functioning program.

First, you have the outside malicious sources, and don't say it won't happen to you, as the odds are really not in your favor.

Then we come to authentication, where we, both have to think about your security, as well as the safety of your users.

After the users of your app have registered, or logged in, we split them up. All are not authorized equally, to put it simply. You might have administrators, with all the privileges, and a bunch of other roles, to whom you may allow different actions.

Finally, we have to validate the incoming data, and if necessary censor the output.

Whether the threat is coming from a malicious outsider, or an uninformed client/employee, we'll deal with it with extreme prejudice, as they say in the movies.

Unless you're going for a RESTful API, you're going to want a user interface. Your site being pretty is not the only thing you need to consider, as the functionality is much more important. Of course, we'll make your pages look great, but first we need to think about the user experience.

A call to action button needs to be in the right place, in order to well, call to action. Your services, or products need to have a front row seat, or else your customers will be looking at a pretty, but also confusing website.

Some larger projects, make use of a whole user interface system and if that's your need, we'll make that happen.

After we've settled on a design, we start working on the markup, which makes the bones of your web application.

Why do we use JavaScript? That question has somewhat fallen out of fashion, because now you can do anything with the language. Whether you're utilizing a front end framework like React or Angular, or you're using NodeJs to handle your back-end business logic, JavaScript has become one of the top players.

However, in a more traditional meaning, we use it to make our websites behave.

For example, we can exploit the language to animate elements on certain conditions. Don't worry, I won't make your button dance on the screen, I'm not that tacky. But how about make it slide into view, when your client reaches a particular product on the page.

We can also use JavaScript, to communicate with external APIs. There are countless implementations of very simple services, which you might like to include on your page, and we can fetch them, using this language, that runs in every browser.

All in all, we need JavaScript to make the user's experience, the best it can be, even if we're not building a pure JS website.

When we create new style and design, first we need to make sure it actually does offer something fresh, but also follows the client's philosophy. Clean and elegant with lots of white space, or maybe a more traditional look, that's for you to decide and for us to implement.

We use CSS to style our websites and while we may utilize a preprocessor like Sass, the end product is still the same.

We pick a color palette, where we choose the primary and secondary, as well as the accent pigment in order to distinguish our app from the rest. During this process we need to consider contrast and make sure our shades complement each other.

We pick our Typography, namely the font/fonts - family, size, weight and we make sure these different styles go well together. After all, your customers are going to spend most of their time on your page, looking at text.

We need to make sure our styles are intuitive. That means we don't make our delete button blue and we don't use Comics Sans font family for a law firm website.

Responsive design isn't really a great name, for what it actually means and may confuse people. It basically means that we consider different viewing devices when we style our websites, so that they look good on all of them.

It is also required that we maintain the same functionality and retain, if not improve the user experience on our pages. To achieve this, we can utilize a framework like Bootstrap, or build something unique with the help of technologies like Flexbox or CSS Grid. Each comes with an advantage and a cost, and we'll decide that together.

Now, I know you may think it's a cliche, but our philosophy is human approach. We give our all on each project and strive to create unique solutions, that separates our design from others.

We also love to communicate with our clients and cherish their input, always trying to make sites that show your passion, as well as ours.

That collaboration, I call magic.

Everyone makes mistakes and we're not going to pretend, we're not human. Whether it was us, or maybe someone who came before us, we'll fix it

To achieve this, we use a philosophy called Test Driven Programming, where we constantly run tests in order to minimize the bugs.

Still, some may still persist and that's where you come to play. Good feedback from both yourself and your clients is the best way to make mistakes go away as fast as possible.

Again, even if it wasn't us who left the bugs, you can still contact us and we'll eradicate them.

After it's all said and done we're pushing our project to the server and running the final tests.

We'll also help you pick a good domain name and also choose a hosting package worthy of your needs.

Our final services include setting up your email accounts, creating a server side database and inserting the initial data. We'll also help you get acquainted with the content management system, if that was part of your app.

Congratulations, it's done. All you're left to do is celebrate and spread the word around.

Remember, we're there for you and welcome the feedback.

Enjoy