I'm afraid that IP addresses are a very real part of working on networks today, and making them relatively easy to remember is pretty important. Mixing numbers and letters together in hexadecimal (a numbering system humans don't use) was something cobbled together by some tit who had no idea about the practicalities of maintaining a network.
The base in which you choose to represent the number is not really relevant. The computer is storing it all in binary anyway. You can write your applications to accept them in decimal if you wish, and let the computer convert them to binary. The reason that the standard is hexadecimal is because it is much quicker to convert from hex to binary in your head than from decimal to binary.
The binary representation allows you to see the network topology (and hence the routing rules) much more quickly. There's a reason that 255 shows up so often in IPv4 address, it's 0xff which is eight ones in binary, and when used as a mask it selects all the bits in the octet. Similarly, something like 248 is 0xf8 which is 11111000 in binary, which makes it much easier to see how the subnet routing is set up.
The philosophy of using hex is that hex is what networking experts would prefer to work in. So, give them hex addresses, and let the standard users just use DHCP-like services and never worry about IP addresses.