It is not clear what attack you are attempting to defend against. If you want this value to be unpredictable then what you are missing is a Cryptogrpahic Nonce. The application ID and the UserId should be randomly generated large numbers. The idea behind David Crawford's token is that no 2 applications will ever generate the same id, which is a valid approach to generate a nonce for applications that are widely distributed.
The problem with using "user_id + 1000" is that it is trivial to predict.
To generate unique id that is also extremely difficult to predict (A Cryptogrpahic Nonce) you should do the following. First you should start with a very large randomly generated number, then append the current timestamp and pass it all to a message digest function such as md4. Md4 generates a number that is 2^128 in size and usually in base16. Keep in mind that collision generation does not compromise the integrity of a nonce, so md4 or md5 is perfectly acceptable from a secuirty perspective. Note, that there is a lot of disagreement over what the best random number generator is, but keep in mind that a random number generator can generate the same number twice, but the current time stamp is always unique for that execute frame.